diff --git a/src/diagnostics/diagnostic-items.md b/src/diagnostics/diagnostic-items.md index 9360427d6..4000cbdb8 100644 --- a/src/diagnostics/diagnostic-items.md +++ b/src/diagnostics/diagnostic-items.md @@ -48,7 +48,7 @@ A new diagnostic item can be added with these two steps: For the naming conventions of diagnostic items, please refer to [*Naming Conventions*](#naming-conventions). -2. +2. Diagnostic items in code are accessed via symbols in [`rustc_span::symbol::sym`]. To add your newly-created diagnostic item, diff --git a/src/diagnostics/error-codes.md b/src/diagnostics/error-codes.md index 1693432b9..98d9a7ab0 100644 --- a/src/diagnostics/error-codes.md +++ b/src/diagnostics/error-codes.md @@ -10,7 +10,7 @@ explanation: new error codes must include them. Note that not all _historical_ The explanations are written in Markdown (see the [CommonMark Spec] for specifics around syntax), and all of them are linked in the [`rustc_error_codes`] crate. Please read [RFC 1567] for details on how to format and write long error -codes. As of February 2023, there is an +codes. As of August 2025, there is an effort[^new-explanations] to replace this largely outdated RFC with a new more flexible standard. diff --git a/src/diagnostics/lintstore.md b/src/diagnostics/lintstore.md index 7b98bc621..f0d349c91 100644 --- a/src/diagnostics/lintstore.md +++ b/src/diagnostics/lintstore.md @@ -21,7 +21,7 @@ which boils down to a static with type [`&rustc_lint_defs::Lint`] as the macro is somewhat unwieldy to add new fields to, like all macros). -As of Aug 2022, +As of Aug 2025, we lint against direct declarations without the use of the macro. Lint declarations don't carry any "state" - they are merely global identifiers diff --git a/src/diagnostics/translation.md b/src/diagnostics/translation.md index 58d75f54a..5d143da2b 100644 --- a/src/diagnostics/translation.md +++ b/src/diagnostics/translation.md @@ -2,12 +2,12 @@
rustc's current diagnostics translation infrastructure (as of - October 2024 + August 2025 ) unfortunately causes some friction for compiler contributors, and the current infrastructure is mostly pending a redesign that better addresses needs of both compiler contributors and translation teams. Note that there is no current active redesign proposals (as of - October 2024 + August 2025 )! Please see the tracking issue diff --git a/src/tests/ci.md b/src/tests/ci.md index a8cc95912..95850c07c 100644 --- a/src/tests/ci.md +++ b/src/tests/ci.md @@ -22,7 +22,7 @@ jobs](#modifying-ci-jobs). ## CI workflow - + Our CI is primarily executed on [GitHub Actions], with a single workflow defined in [`.github/workflows/ci.yml`], which contains a bunch of steps that are diff --git a/src/tests/directives.md b/src/tests/directives.md index fbbeb7e97..6cf73909b 100644 --- a/src/tests/directives.md +++ b/src/tests/directives.md @@ -42,7 +42,7 @@ not be exhaustive. Directives can generally be found by browsing the ### Assembly - + | Directive | Explanation | Supported test suites | Possible values | |-------------------|-------------------------------|-----------------------|----------------------------------------| @@ -113,7 +113,7 @@ for more details. | `known-bug` | No error annotation needed due to known bug | `ui`, `crashes`, `incremental` | Issue number `#123456` | | `compare-output-by-lines` | Compare the output by lines, rather than as a single string | All | N/A | -[^check_stdout]: presently this has a weird quirk +[^check_stdout]: presently this has a weird quirk where the test binary's stdout and stderr gets concatenated and then `error-pattern`s are matched on this combined output, which is ??? slightly questionable to say the least. diff --git a/src/tests/misc.md b/src/tests/misc.md index 39f881748..ed80c6c34 100644 --- a/src/tests/misc.md +++ b/src/tests/misc.md @@ -2,7 +2,7 @@ ## `RUSTC_BOOTSTRAP` and stability - + This is a bootstrap/compiler implementation detail, but it can also be useful for testing: