chore: fix some typos in comments

Signed-off-by: whosehang <whosehang@outlook.com>
This commit is contained in:
whosehang 2024-04-24 13:58:51 +08:00
parent c1feb3ecee
commit 65d7c1d2d6
9 changed files with 9 additions and 9 deletions

View File

@ -1251,7 +1251,7 @@ struct HygieneDecodeContextInner {
// global `HygieneData`. When we deserialize a `SyntaxContext`, we need to create // global `HygieneData`. When we deserialize a `SyntaxContext`, we need to create
// a new id in the global `HygieneData`. This map tracks the ID we end up picking, // a new id in the global `HygieneData`. This map tracks the ID we end up picking,
// so that multiple occurrences of the same serialized id are decoded to the same // so that multiple occurrences of the same serialized id are decoded to the same
// `SyntaxContext`. This only stores `SyntaxContext`s which are completly decoded. // `SyntaxContext`. This only stores `SyntaxContext`s which are completely decoded.
remapped_ctxts: Vec<Option<SyntaxContext>>, remapped_ctxts: Vec<Option<SyntaxContext>>,
/// Maps serialized `SyntaxContext` ids that are currently being decoded to a `SyntaxContext`. /// Maps serialized `SyntaxContext` ids that are currently being decoded to a `SyntaxContext`.

View File

@ -227,7 +227,7 @@ pub enum TyKind<I: Interner> {
/// A placeholder type, used during higher ranked subtyping to instantiate /// A placeholder type, used during higher ranked subtyping to instantiate
/// bound variables. /// bound variables.
/// ///
/// It is conventional to render anonymous placeholer types like `!N` or `!U_N`, /// It is conventional to render anonymous placeholder types like `!N` or `!U_N`,
/// where `N` is the placeholder variable's anonymous index (which corresponds /// where `N` is the placeholder variable's anonymous index (which corresponds
/// to the bound variable's index from the binder from which it was instantiated), /// to the bound variable's index from the binder from which it was instantiated),
/// and `U` is the universe index in which it is instantiated, or totally omitted /// and `U` is the universe index in which it is instantiated, or totally omitted

View File

@ -153,7 +153,7 @@ pub fn from_usize(x: &usize) -> Argument<'_> {
/// ///
/// # Safety /// # Safety
/// ///
/// This argument must actually be a placeholer argument. /// This argument must actually be a placeholder argument.
/// ///
// FIXME: Transmuting formatter in new and indirectly branching to/calling // FIXME: Transmuting formatter in new and indirectly branching to/calling
// it here is an explicit CFI violation. // it here is an explicit CFI violation.

View File

@ -73,7 +73,7 @@ Tests can be run on AArch64 Windows 11 devices.
## Cross-compilation toolchains and C code ## Cross-compilation toolchains and C code
C code can be built using the Arm64-targetting MSVC or Clang toolchain. C code can be built using the Arm64-targeting MSVC or Clang toolchain.
To compile: To compile:

View File

@ -59,7 +59,7 @@ languages compiled to WebAssembly, for example C/C++. Any ABI differences or
mismatches are considered bugs that need to be fixed. mismatches are considered bugs that need to be fixed.
By default the WASI targets in Rust ship in rustup with a precompiled copy of By default the WASI targets in Rust ship in rustup with a precompiled copy of
[`wasi-libc`] meaning that a WebAssembly-targetting-Clang is not required to [`wasi-libc`] meaning that a WebAssembly-targeting-Clang is not required to
use the WASI targets from Rust. If there is no actual interoperation with C use the WASI targets from Rust. If there is no actual interoperation with C
then `rustup target add wasm32-wasip1` is all that's needed to get then `rustup target add wasm32-wasip1` is all that's needed to get
started with WASI. started with WASI.

View File

@ -417,7 +417,7 @@ warning: 1 warning emitted
This lint is **warn-by-default**. It detects explicit links that are the same This lint is **warn-by-default**. It detects explicit links that are the same
as computed automatic links. as computed automatic links.
This usually means the explicit links are removeable. For example: This usually means the explicit links are removable. For example:
```rust ```rust
#![warn(rustdoc::redundant_explicit_links)] // note: unnecessary - warns by default. #![warn(rustdoc::redundant_explicit_links)] // note: unnecessary - warns by default.

View File

@ -168,4 +168,4 @@ render differently in this case:
``` ```
`1.` and `2.` will be displayed as is in the rendered documentation (ie, `[a]` and `[b][c]`) `1.` and `2.` will be displayed as is in the rendered documentation (ie, `[a]` and `[b][c]`)
whereas `3.` and `4.` will be replaced by a link targetting `e` for `[d](e)` and `g` for `[f]`. whereas `3.` and `4.` will be replaced by a link targeting `e` for `[d](e)` and `g` for `[f]`.

View File

@ -187,7 +187,7 @@ macro_rules! declare_rustdoc_lint {
declare_rustdoc_lint! { declare_rustdoc_lint! {
/// This lint is **warn-by-default**. It detects explicit links that are the same /// This lint is **warn-by-default**. It detects explicit links that are the same
/// as computed automatic links. This usually means the explicit links are removeable. /// as computed automatic links. This usually means the explicit links are removable.
/// This is a `rustdoc` only lint, see the documentation in the [rustdoc book]. /// This is a `rustdoc` only lint, see the documentation in the [rustdoc book].
/// ///
/// [rustdoc book]: ../../../rustdoc/lints.html#redundant_explicit_links /// [rustdoc book]: ../../../rustdoc/lints.html#redundant_explicit_links

View File

@ -314,7 +314,7 @@ pub enum StructKind {
/// All [`Id`]'s will point to [`ItemEnum::StructField`]. Private and /// All [`Id`]'s will point to [`ItemEnum::StructField`]. Private and
/// `#[doc(hidden)]` fields will be given as `None` /// `#[doc(hidden)]` fields will be given as `None`
Tuple(Vec<Option<Id>>), Tuple(Vec<Option<Id>>),
/// A struct with nammed fields. /// A struct with named fields.
/// ///
/// ```rust /// ```rust
/// pub struct PlainStruct { x: i32 } /// pub struct PlainStruct { x: i32 }