@@ -37,7 +37,7 @@ The name resolution lives in the `librustc_resolve` crate, with the meat in
37
37
38
38
## Namespaces
39
39
40
- Different kind of symbols live in different namespaces ‒ eg . types don't
40
+ Different kind of symbols live in different namespaces ‒ e.g . types don't
41
41
clash with variables. This usually doesn't happen, because variables start with
42
42
lower-case letter while types with upper case one, but this is only a
43
43
convention. This is legal Rust code that'll compile (with warnings):
@@ -99,7 +99,7 @@ fn do_something<T: Default>(val: T) { // <- New rib in both types and values (1)
99
99
100
100
Because the rules for different namespaces are a bit different, each namespace
101
101
has its own independent rib stack that is constructed in parallel to the others.
102
- In addition, there's also a rib stack for local labels (eg . names of loops or
102
+ In addition, there's also a rib stack for local labels (e.g . names of loops or
103
103
blocks), which isn't a full namespace in its own right.
104
104
105
105
## Overall strategy
@@ -129,7 +129,7 @@ Still, it probably provides useful first guidepost to what happens in there.
129
129
following stages of compilation?
130
130
* Who calls it and how it is actually used.
131
131
* Is it a pass and then the result is only used, or can it be computed
132
- incrementally (eg . for RLS)?
132
+ incrementally (e.g . for RLS)?
133
133
* The overall strategy description is a bit vague.
134
134
* Where does the name ` Rib ` come from?
135
135
* Does this thing have its own tests, or is it tested only as part of some e2e
0 commit comments