Skip to content

Commit 9b3803d

Browse files
phanschmark-i-m
authored andcommitted
Don't reference librustc_resolve just yet.
It's mentioned further down with more details.
1 parent c28c5e8 commit 9b3803d

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/name-resolution.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -12,10 +12,10 @@ let x: x = 1;
1212
let y: x = 2;
1313
```
1414

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.
15+
How do we know on line 3 whether `x` is a type (u32) or a value (1)? These
16+
conflicts are resolved during name resolution. In this specific case, name
17+
resolution defines that type names and variable names live in separate
18+
namespaces and therefore can co-exist.
1919

2020
The name resolution in Rust is a two-phase process. In the first phase, which runs
2121
during macro expansion, we build a tree of modules and resolve imports. Macro

0 commit comments

Comments
 (0)