We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
1 parent c28c5e8 commit 9b3803dCopy full SHA for 9b3803d
src/name-resolution.md
@@ -12,10 +12,10 @@ let x: x = 1;
12
let y: x = 2;
13
```
14
15
-How do we know on line 3 whether `x` is a type (u32) or a value (1)?
16
-These conflicts are resolved in `librustc_resolve`.
17
-In this specific case, name resolution defines that type names and variable
18
-names live in separate namespaces and therefore can co-exist.
+How do we know on line 3 whether `x` is a type (u32) or a value (1)? These
+conflicts are resolved during name resolution. In this specific case, name
+resolution defines that type names and variable names live in separate
+namespaces and therefore can co-exist.
19
20
The name resolution in Rust is a two-phase process. In the first phase, which runs
21
during macro expansion, we build a tree of modules and resolve imports. Macro
0 commit comments