Rollup merge of #104505 - WaffleLapkin:no-double-spaces-in-comments, r=jackh726
Remove double spaces after dots in comments Most of the comments do not have double spaces, so I assume these are typos.
This commit is contained in:
commit
68f12338af
158 changed files with 333 additions and 313 deletions
|
@ -148,7 +148,7 @@ impl<'tcx> ProjectionCandidateSet<'tcx> {
|
|||
}
|
||||
|
||||
// Prefer where-clauses. As in select, if there are multiple
|
||||
// candidates, we prefer where-clause candidates over impls. This
|
||||
// candidates, we prefer where-clause candidates over impls. This
|
||||
// may seem a bit surprising, since impls are the source of
|
||||
// "truth" in some sense, but in fact some of the impls that SEEM
|
||||
// applicable are not, because of nested obligations. Where
|
||||
|
@ -1034,7 +1034,7 @@ fn opt_normalize_projection_type<'a, 'b, 'tcx>(
|
|||
}
|
||||
Err(ProjectionCacheEntry::InProgress) => {
|
||||
// Under lazy normalization, this can arise when
|
||||
// bootstrapping. That is, imagine an environment with a
|
||||
// bootstrapping. That is, imagine an environment with a
|
||||
// where-clause like `A::B == u32`. Now, if we are asked
|
||||
// to normalize `A::B`, we will want to check the
|
||||
// where-clauses in scope. So we will try to unify `A::B`
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue