Update date references for 2026-05 triage (#2861)#2872
Open
santihdzs wants to merge 1 commit into
Open
Conversation
Collaborator
|
jyn514
requested changes
May 21, 2026
Member
There was a problem hiding this comment.
Hi @santihdzs, did you generate this PR using an LLM? it's ok if you did, but please disclose beforehand that you did so.
| # `minicore` test auxiliary: using `core` stubs | ||
|
|
||
| <!-- date-check: Oct 2025 --> | ||
| <!-- date-check: May 2026 --> |
Member
There was a problem hiding this comment.
I don't see any date here at all. Can we just remove the date-check comment?
| ## `RUSTC_BOOTSTRAP` and stability | ||
|
|
||
| <!-- date-check: Nov 2024 --> | ||
| <!-- date-check: May 2026 --> |
Comment on lines
-444
to
+457
| <!-- date-check --> Nov 2025 | ||
| <!-- date-check --> May 2026 | ||
| ``` | ||
|
|
||
| Example: | ||
|
|
||
| ```md | ||
| As of <!-- date-check --> Nov 2025, the foo did the bar. | ||
| As of <!-- date-check --> 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 | ||
| <!-- date-check: Nov 2025 --> | ||
| <!-- date-check: May 2026 --> |
Member
There was a problem hiding this comment.
this is in the contributing guide and not tied to anything specific. it doesn't need updating.
| @@ -1,4 +1,4 @@ | |||
| <!-- date-check: Jul 2025 --> | |||
| <!-- date-check: May 2026 --> | |||
| 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 --> | ||
| <!-- date-check: May 2026 --> |
| 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. |
Collaborator
|
Reminder, once the PR becomes ready for a review, use |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #2861.
Updated date references to May 2026 in:
Skipped lldb-visualizers.md and opaque-types-type-alias-impl-trait.md
as those reference external dependencies needing deeper verification.
r? rust-lang/rustc-dev-guide