Skip to content

Commit e37eb67

Browse files
authored
Merge pull request #2513 from rust-lang/tshepang/typos
fix some typos
2 parents 4de2069 + 72c8958 commit e37eb67

File tree

5 files changed

+6
-6
lines changed

5 files changed

+6
-6
lines changed

src/building/suggested.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -162,7 +162,7 @@ create a `.vim/coc-settings.json`. The settings can be edited with
162162
[`src/etc/rust_analyzer_settings.json`].
163163

164164
Another way is without a plugin, and creating your own logic in your
165-
configuration. The following code will work for any checkout of rust-lang/rust (newer than Febuary 2025):
165+
configuration. The following code will work for any checkout of rust-lang/rust (newer than February 2025):
166166

167167
```lua
168168
local function expand_config_variables(option)

src/hir/ambig-unambig-ty-and-consts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ Note that places 3 and 4 would never actually be possible to encounter as we alw
3838
This has a few failure modes:
3939
- People may write visitors which check for `GenericArg::Infer` but forget to check for `hir::TyKind/ConstArgKind::Infer`, only handling infers in ambig positions by accident.
4040
- People may write visitors which check for `hir::TyKind/ConstArgKind::Infer` but forget to check for `GenericArg::Infer`, only handling infers in unambig positions by accident.
41-
- People may write visitors which check for `GenerArg::Type/Const(TyKind/ConstArgKind::Infer)` and `GenerigArg::Infer`, not realising that we never represent inferred types/consts in ambig positions as a `GenericArg::Type/Const`.
41+
- People may write visitors which check for `GenericArg::Type/Const(TyKind/ConstArgKind::Infer)` and `GenericArg::Infer`, not realising that we never represent inferred types/consts in ambig positions as a `GenericArg::Type/Const`.
4242
- People may write visitors which check for *only* `TyKind::Infer` and not `ConstArgKind::Infer` forgetting that there are also inferred const arguments (and vice versa).
4343

4444
To make writing HIR visitors less error prone when caring about inferred types/consts we have a relatively complex system:
@@ -60,4 +60,4 @@ This has a number of benefits:
6060
[ambig_arg]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_hir/hir/enum.AmbigArg.html
6161
[visit_ty]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_hir/intravisit/trait.Visitor.html#method.visit_ty
6262
[visit_const_arg]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_hir/intravisit/trait.Visitor.html#method.visit_const_arg
63-
[visit_infer]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_hir/intravisit/trait.Visitor.html#method.visit_infer
63+
[visit_infer]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_hir/intravisit/trait.Visitor.html#method.visit_infer

src/rustdoc-internals/rustdoc-test-suite.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Internally, [`compiletest`] invokes the supplementary checker script [`htmldocck
2020

2121
Directives to HtmlDocCk are assertions that place constraints on the generated HTML.
2222
They look similar to those given to `compiletest` in that they take the form of `//@` comments
23-
but ultimately, they are completey distinct and processed by different programs.
23+
but ultimately, they are completely distinct and processed by different programs.
2424

2525
[XPath] is used to query parts of the HTML document tree.
2626

src/tests/compiletest.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ on if or how to run the test, what behavior to expect, and more. See
2929
[directives](directives.md) and the test suite documentation below for more details
3030
on these annotations.
3131

32-
See the [Adding new tests](adding.md) and [Best practies](best-practices.md)
32+
See the [Adding new tests](adding.md) and [Best practices](best-practices.md)
3333
chapters for a tutorial on creating a new test and advice on writing a good
3434
test, and the [Running tests](running.md) chapter on how to run the test suite.
3535

src/ty_module/instantiating_binders.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ This end result is incorrect as we had two separate binders introducing their ow
7777

7878
While in theory we could make this work it would be quite involved and more complex than the current setup, we would have to:
7979
- "rewrite" bound variables to have a higher `DebruijnIndex` whenever instantiating a `Binder`/`EarlyBinder` with a `Bound` ty/const/region
80-
- When inferring an inference variable to a bound var, if that bound var is from a binder enterred after creating the infer var, we would have to lower the `DebruijnIndex` of the var.
80+
- When inferring an inference variable to a bound var, if that bound var is from a binder entered after creating the infer var, we would have to lower the `DebruijnIndex` of the var.
8181
- Separately track what binder an inference variable was created inside of, also what the innermost binder it can name parameters from (currently we only have to track the latter)
8282
- When resolving inference variables rewrite any bound variables according to the current binder depth of the infcx
8383
- Maybe more (while writing this list items kept getting added so it seems naive to think this is exhaustive)

0 commit comments

Comments
 (0)