Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A problem arose in CamFort with the location of declarations being misreported to the wrong file (camfort/camfort#185). It turns out this comes down to the structure of mod file analysis, where all the
use
d modules get their name space inserted into the module map and so it cannot be distinguished whether a variable was declared in this module or an imported one. This PR fixes this by adding information into theNameType
data structure about whether a variable isLocal
orImported
. A module map can then be 'localised' withlocalisedModuleMap
which removes from a mod map any imported declarations. This fixes the bug in CamFort.An accompanying test was added in
ModFileSpec
The
genUniqNameToFilenameMap :: ModFiles -> M.Map F.Name String
applies this localisation.