mirror
/
rustc-dev-guide
mirror of https://github.com/rust-lang/rustc-dev-guide.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #2367 from rust-lang/rustc-pull 

Rustc pull update
This commit is contained in:
Tshepang Mbambo 2025-05-01 07:01:46 +02:00 committed by GitHub
parent 4d2e6a9dc6 f6524cb54d
commit 72a9e36e04
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
rust-version
View File

@ -1 +1 @@
deb947971c8748f5c6203548ce4af9022f21eaf0 0c33fe2c3d3eecadd17a84b110bb067288a64f1c

6
src/tests/ui.md
View File

@ -372,9 +372,9 @@ E.g. use `//@ dont-require-annotations: NOTE` to annotate notes selectively.
Avoid using this directive for `ERROR`s and `WARN`ings, unless there's a serious reason, like Avoid using this directive for `ERROR`s and `WARN`ings, unless there's a serious reason, like
target-dependent compiler output. target-dependent compiler output.
Missing diagnostic kinds (`//~ message`) are currently accepted, but are being phased away. Some diagnostics are never required to be line-annotated, regardless of their kind or directives,
They will match any compiler output kind, but will not force exhaustive annotations for that kind. for example secondary lines of multiline diagnostics,
Prefer explicit kind and `//@ dont-require-annotations` to achieve the same effect. or ubiquitous diagnostics like `aborting due to N previous errors`.
UI tests use the `-A unused` flag by default to ignore all unused warnings, as UI tests use the `-A unused` flag by default to ignore all unused warnings, as
unused warnings are usually not the focus of a test. However, simple code unused warnings are usually not the focus of a test. However, simple code