Rollup merge of #95497 - nyurik:compiler-spell-comments, r=compiler-errors
Spellchecking compiler comments This PR cleans up the rest of the spelling mistakes in the compiler comments. This PR does not change any literal or code spelling issues.
This commit is contained in:
commit
1b7d6dbd30
111 changed files with 164 additions and 164 deletions
|
@ -580,7 +580,7 @@ impl<'a, 'tcx> Decodable<DecodeContext<'a, 'tcx>> for Span {
|
|||
//
|
||||
// Suppose that we're currently compiling crate A, and start deserializing
|
||||
// metadata from crate B. When we deserialize a Span from crate B's metadata,
|
||||
// there are two posibilites:
|
||||
// there are two possibilities:
|
||||
//
|
||||
// 1. The span references a file from crate B. This makes it a 'local' span,
|
||||
// which means that we can use crate B's serialized source map information.
|
||||
|
|
|
@ -271,7 +271,7 @@ impl<'a, 'tcx> Encodable<EncodeContext<'a, 'tcx>> for Span {
|
|||
// from. We use `TAG_VALID_SPAN_FOREIGN` to indicate that a `CrateNum` should
|
||||
// be deserialized after the rest of the span data, which tells the deserializer
|
||||
// which crate contains the source map information.
|
||||
// 2. This span comes from our own crate. No special hamdling is needed - we just
|
||||
// 2. This span comes from our own crate. No special handling is needed - we just
|
||||
// write `TAG_VALID_SPAN_LOCAL` to let the deserializer know that it should use
|
||||
// our own source map information.
|
||||
//
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue