Fix groups inside namespaces in build!
#806
Merged
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.
Currently
BuildMacro::parse
tracks the current namespace-path with asingle mutable string throughout the walking of the
UseTree
. When thewalking of a
UseTree::Path
is completed, it incorrectly forgets to popthat sub-namespace off the namespace-path string. As a result, when a
UseTree::Group
contains more than one sub-UseTree
s, lattersub-
UseTree
s are walked with a namespace-path that has the leafsub-namespaces of the previous sub-
UseTree
s incorrectly infixed intoit:
This commit fixes that by cloning the namespace-path string when walking
a
UseTree::Group
.It also changes the diagnostics when trying to importing a nonexistent
item in the global namespace from
.Foo
to(global namespace).Foo
.