diff options
| author | klensy <klensy@users.noreply.github.com> | 2021-04-19 15:57:08 +0300 |
|---|---|---|
| committer | klensy <klensy@users.noreply.github.com> | 2021-04-19 15:57:08 +0300 |
| commit | f43ee8ebf696eec5a8a844629e4f7e910f9f0afd (patch) | |
| tree | bf829ad19f0402dd8c1148d5df4d6c1edce87923 /compiler/rustc_resolve | |
| parent | 62652865b6029b4776a7c03efa13a37b15c9b953 (diff) | |
| download | rust-f43ee8ebf696eec5a8a844629e4f7e910f9f0afd.tar.gz rust-f43ee8ebf696eec5a8a844629e4f7e910f9f0afd.zip | |
fix few typos
Diffstat (limited to 'compiler/rustc_resolve')
| -rw-r--r-- | compiler/rustc_resolve/src/late/lifetimes.rs | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/compiler/rustc_resolve/src/late/lifetimes.rs b/compiler/rustc_resolve/src/late/lifetimes.rs index a93afedf7f6..fc1ea4ec846 100644 --- a/compiler/rustc_resolve/src/late/lifetimes.rs +++ b/compiler/rustc_resolve/src/late/lifetimes.rs @@ -245,7 +245,7 @@ enum Scope<'a> { opaque_type_parent: bool, /// True only if this `Binder` scope is from the quantifiers on a - /// `PolyTraitRef`. This is necessary for `assocated_type_bounds`, which + /// `PolyTraitRef`. This is necessary for `associated_type_bounds`, which /// requires binders of nested trait refs to be merged. from_poly_trait_ref: bool, @@ -303,7 +303,7 @@ enum Scope<'a> { /// of. Other than that, if ask for bound vars for each, we expect /// `['a, 'b]`. If we *didn't* allow binders before `T`, then we would /// always introduce a binder scope at the inner trait ref. This is great, - /// becauase later on during type-checking, we will ask "what are the late + /// because later on during type-checking, we will ask "what are the late /// bound vars on this trait ref". However, because we allow bound vars on /// the bound itself, we have to have some way of keeping track of the fact /// that we actually want to store the late bound vars as being associated |
