From 56ee20f0015913bb5f0d4b8e54ffc9d129df70c0 Mon Sep 17 00:00:00 2001 From: Santi Hernandez Date: Thu, 14 May 2026 18:58:21 -0600 Subject: [PATCH] Update date references for 2026-05 triage (#2861) --- src/contributing.md | 6 +++--- src/implementing-new-features.md | 2 +- src/normalization.md | 2 +- src/rustdoc-internals.md | 2 +- src/tests/minicore.md | 2 +- src/tests/misc.md | 2 +- 6 files changed, 8 insertions(+), 8 deletions(-) diff --git a/src/contributing.md b/src/contributing.md index 7f4779515b..5b00c418ec 100644 --- a/src/contributing.md +++ b/src/contributing.md @@ -441,20 +441,20 @@ Just a few things to keep in mind: For the action to pick the date, add a special annotation before specifying the date: ```md - Nov 2025 + May 2026 ``` Example: ```md - As of Nov 2025, the foo did the bar. + As of May 2026, the foo did the bar. ``` For cases where the date should not be part of the visible rendered output, use the following instead: ```md - + ``` - A link to a relevant WG, tracking issue, `rustc` rustdoc page, or similar, that may provide diff --git a/src/implementing-new-features.md b/src/implementing-new-features.md index a34c812f72..ec2082e1ee 100644 --- a/src/implementing-new-features.md +++ b/src/implementing-new-features.md @@ -1,4 +1,4 @@ - + # Implementing new language features diff --git a/src/normalization.md b/src/normalization.md index b458b04c17..5e69222db9 100644 --- a/src/normalization.md +++ b/src/normalization.md @@ -164,7 +164,7 @@ In this example: When interfacing with the type system it will often be the case that it's necessary to request a type be normalized. There are a number of different entry points to the underlying normalization logic and each entry point should only be used in specific parts of the compiler. - + An additional complication is that the compiler is currently undergoing a transition from the old trait solver to the new trait solver. As part of this transition our approach to normalization in the compiler has changed somewhat significantly, resulting in some normalization entry points being "old solver only" slated for removal in the long-term once the new solver has stabilized. The transition can be tracked via the [WG-trait-system-refactor](https://github.com/rust-lang/rust/labels/WG-trait-system-refactor) label in Github. diff --git a/src/rustdoc-internals.md b/src/rustdoc-internals.md index f3fd47812a..df8adab351 100644 --- a/src/rustdoc-internals.md +++ b/src/rustdoc-internals.md @@ -222,7 +222,7 @@ directly, even during `HTML` generation. This [didn't used to be the case], and a lot of `rustdoc`'s architecture was designed around not doing that, but a `TyCtxt` is now passed to `formats::renderer::run_format`, which is used to -run generation for both `HTML` and the (unstable as of Nov 2025) JSON format. +run generation for both `HTML` and the (unstable as of May 2026) JSON format. This change has allowed other changes to remove data from the "clean" [`AST`][ast] that can be easily derived from `TyCtxt` queries, and we'll usually accept diff --git a/src/tests/minicore.md b/src/tests/minicore.md index 0fd7af7c60..709feecd29 100644 --- a/src/tests/minicore.md +++ b/src/tests/minicore.md @@ -1,6 +1,6 @@ # `minicore` test auxiliary: using `core` stubs - + [`tests/auxiliary/minicore.rs`][`minicore`] is a test auxiliary for ui/codegen/assembly/mir-opt test suites. It provides `core` stubs for tests that need to diff --git a/src/tests/misc.md b/src/tests/misc.md index cc8f501224..8fecbdd74a 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: