You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
7336: Rename `CrateDefMap` to `DefMap` r=matklad a=jonas-schievink
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 a `DefMap` that has a reference to the parent `DefMap`, which is either the one computed for the containing block expression, or the crate's root `DefMap`. Name resolution will fall back to a name in the parent `DefMap` 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 these `DefMap`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
Co-authored-by: Jonas Schievink <jonasschievink@gmail.com>
We didn't ticked the boxes, but we made a great progress.
Understandably, actually ticking the boxes turns out to be challenging. To get better at these, we decided to officially install @matklad as "cheif makes-sure-that-the-boxes-are-ticked officer" for the next cycle.
This the steering issue -- it documents our roadmap for the next six weeks!
Steering meeting: link
The overall theme of the sprint is end-user experience. Specific subissues:
Refactor import resolution (Mostly resolved by Unleash inner item resolution to users #7614 / infer: update resolver when descending into block #7627CrateDefMap
) #5922The text was updated successfully, but these errors were encountered: