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.
I propose handling local items by computing a
DefMap
for every block expression, using the regular (early) name resolution algorithm. The result of that will be aDefMap
that has a reference to the parentDefMap
, which is either the one computed for the containing block expression, or the crate's rootDefMap
. Name resolution will fall back to a name in the parentDefMap
if it cannot be resolved in the inner block.The
DefMap
s computed for block expressions will go through a separate query that can be garbage-collected much more aggressively, since theseDefMap
s should be cheap to compute and are never part of a crate's public API.The first step towards that is to make
CrateDefMap
not specific to crates anymore, hence this rename (if this plans sounds reasonable).cc #7325 and #1165