Skip to content

Commit

Permalink
Triage some date-check items (#1513)
Browse files Browse the repository at this point in the history
  • Loading branch information
camelid authored Nov 26, 2022
1 parent 0bd5bd1 commit 2889c29
Show file tree
Hide file tree
Showing 6 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion src/building/suggested.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ You can also install the hook as a step of running `./x.py setup`!
a file. By default, `rust-analyzer` runs the `cargo check` and `rustfmt`
commands, but you can override these commands to use more adapted versions
of these tools when hacking on `rustc`. For example, for Visual Studio Code,
you can write: <!-- date-check: apr 2022 --><!-- the date comment is for the edition below -->
you can write: <!-- date-check: nov 2022 --><!-- the date comment is for the edition below -->

```JSON
{
Expand Down
2 changes: 1 addition & 1 deletion src/conventions.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Formatting is checked by the `tidy` script. It runs automatically when you do

If you want to use format-on-save in your editor, the pinned version of
`rustfmt` is built under `build/<target>/stage0/bin/rustfmt`. You'll have to
pass the <!-- date-check: April 2022 --> `--edition=2021` argument yourself when calling
pass the <!-- date-check: nov 2022 --> `--edition=2021` argument yourself when calling
`rustfmt` directly.

[fmt]: https://github.com/rust-dev-tools/fmt-rfcs
Expand Down
2 changes: 1 addition & 1 deletion src/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -292,7 +292,7 @@ Moreover, the compiler wasn't originally built to use a query system; the query
system has been retrofitted into the compiler, so parts of it are not query-fied
yet. Also, LLVM isn't our code, so that isn't querified either. The plan is to
eventually query-fy all of the steps listed in the previous section,
but as of <!-- date-check --> November 2021, only the steps between HIR and
but as of <!-- date-check --> November 2022, only the steps between HIR and
LLVM IR are query-fied. That is, lexing, parsing, name resolution, and macro
expansion are done all at once for the whole program.

Expand Down
2 changes: 1 addition & 1 deletion src/parallel-rustc.md
Original file line number Diff line number Diff line change
Expand Up @@ -141,7 +141,7 @@ the previous `Data Structures` and `Parallel Iterators`. See [this tracking issu

## Rustdoc

As of <!-- date-check--> May 2022, there are still a number of steps
As of <!-- date-check--> November 2022, there are still a number of steps
to complete before rustdoc rendering can be made parallel. More details on
this issue can be found [here][parallel-rustdoc].

Expand Down
2 changes: 1 addition & 1 deletion src/rustdoc-internals.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ these passes, please let us know!)

[44136]: https://github.com/rust-lang/rust/issues/44136

Here is the list of passes as of <!-- date-check --> May 2022:
Here is the list of passes as of <!-- date-check --> November 2022:

- `calculate-doc-coverage` calculates information used for the `--show-coverage`
flag.
Expand Down
2 changes: 1 addition & 1 deletion src/salsa.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ want to watch [Salsa In More
Depth](https://www.youtube.com/watch?v=i_IhACacPRY), also by Niko
Matsakis.

> As of <!-- date-check --> April 2022, although Salsa is inspired by
> As of <!-- date-check --> November 2022, although Salsa is inspired by
> (among other things) rustc's query system, it is not used directly in rustc.
> It _is_ used in chalk and extensively in `rust-analyzer`, but there are no
> medium or long-term concrete plans to integrate it into the compiler.
Expand Down

0 comments on commit 2889c29

Please sign in to comment.