This crate is responsible for the part of name resolution that doesn’t require type checker.
Module structure of the crate is built here. Paths in macros, imports, expressions, types, patterns are resolved here. Label and lifetime names are resolved here as well.
Type-relative name resolution (methods, fields, associated items) happens in
After we obtain a fresh AST fragment from a macro, code in this module helps to integrate that fragment into the module structures that are already partially built.
A bunch of methods and structures more or less related to resolving imports.
“Late resolution” is the pass that resolves most of names in a crate beside imports and macros. It runs when the crate is fully expanded and its module structure is fully built. So it just walks through the crate and resolves all the expressions, types, etc.
A bunch of methods and structures more or less related to resolving macros and
interface provided by
Resolver to macro expander.
A key that identifies a binding in a given
One node in the tree of modules.
Records a possibly-private value, type, or module definition.
Everything you need to know about a name’s location to resolve it. Serves as a starting point for the scope visitor. This struct is currently used only for early resolution (imports and macros), but not for late resolution yet.
Just a helper ‒ separate structure for each namespace.
The main resolver class.
Nothing really interesting here; it just provides memory for the rest of the crate.
A minimal representation of a path segment. We use this in resolve because we synthesize ‘path
segments’ which don’t have the rest of an AST or HIR
Miscellaneous bits of metadata for better ambiguity error reporting.
Used for better errors for E0773
An intermediate resolution result.
Different kinds of symbols can coexist even if they share the same textual name. Therefore, they each have a separate universe (known as a “namespace”).
A specific scope in which a name can be looked up. This enum is currently used only for early resolution (imports and macros), but not for late resolution yet.
Names from different contexts may want to visit different subsets of all specific scopes with different restrictions when looking up the resolution. This enum is currently used only for early resolution (imports and macros), but not for late resolution yet.
A somewhat inefficient routine to obtain the name of a module.