Skip to content

Commit c28c5e8

Browse files
phanschmark-i-m
authored andcommitted
typo: eg. -> e.g.
1 parent 29b0d1c commit c28c5e8

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/name-resolution.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ The name resolution lives in the `librustc_resolve` crate, with the meat in
3737

3838
## Namespaces
3939

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
4141
clash with variables. This usually doesn't happen, because variables start with
4242
lower-case letter while types with upper case one, but this is only a
4343
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)
9999

100100
Because the rules for different namespaces are a bit different, each namespace
101101
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
103103
blocks), which isn't a full namespace in its own right.
104104

105105
## Overall strategy
@@ -129,7 +129,7 @@ Still, it probably provides useful first guidepost to what happens in there.
129129
following stages of compilation?
130130
* Who calls it and how it is actually used.
131131
* 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)?
133133
* The overall strategy description is a bit vague.
134134
* Where does the name `Rib` come from?
135135
* Does this thing have its own tests, or is it tested only as part of some e2e

0 commit comments

Comments
 (0)