Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion src/implementing-new-features.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,3 @@
<!-- date-check: Jul 2025 -->

# Implementing new language features

Expand Down
1 change: 0 additions & 1 deletion src/normalization.md
Original file line number Diff line number Diff line change
Expand Up @@ -164,7 +164,6 @@ 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.

<!-- date-check: May 2025 -->
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.
Expand Down
2 changes: 1 addition & 1 deletion src/rustdoc-internals.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 <!-- date-check --> Nov 2025) JSON format.
run generation for both `HTML` and the (unstable as of <!-- date-check --> May 2026) JSON format.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 this looks good


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
Expand Down
1 change: 0 additions & 1 deletion src/tests/minicore.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,5 @@
# `minicore` test auxiliary: using `core` stubs

<!-- date-check: Oct 2025 -->

[`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
Expand Down
1 change: 0 additions & 1 deletion src/tests/misc.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,6 @@

## `RUSTC_BOOTSTRAP` and stability

<!-- date-check: Nov 2024 -->

This is a bootstrap/compiler implementation detail, but it can also be useful
for testing:
Expand Down
Loading