Turn remaining non-structural-const-in-pattern lints into hard errors This completes the implementation of https://github.com/rust-lang/rust/issues/120362 by turning our remaining future-compat lints into hard errors: indirect_structural_match and pointer_structural_match. They have been future-compat lints for a while (indirect_structural_match for many years, pointer_structural_match since Rust 1.75 (released Dec 28, 2023)), and have shown up in dependency breakage reports since Rust 1.78 (just released on May 2, 2024). I don't expect a lot of code will still depend on them, but we will of course do a crater run. A lot of cleanup is now possible in const_to_pat, but that is deferred to a later PR. Fixes https://github.com/rust-lang/rust/issues/70861
UI Tests
This folder contains rustc
's
UI tests.
Test Directives (Headers)
Typically, a UI test will have some test directives / headers which are special comments that tell compiletest how to build and intepret a test.
As part of an on-going effort to rewrite compiletest
(see https://github.com/rust-lang/compiler-team/issues/536), a major
change proposal to change legacy compiletest-style headers // <directive>
to ui_test
-style headers
//@ <directive>
was accepted (see
https://github.com/rust-lang/compiler-team/issues/512.
An example directive is ignore-test
. In legacy compiletest style, the header
would be written as
// ignore-test
but in ui_test
style, the header would be written as
//@ ignore-test
compiletest is changed to accept only //@
directives for UI tests
(currently), and will reject and report an error if it encounters any
comments // <content>
that may be parsed as an legacy compiletest-style
test header. To fix this, you should migrate to the ui_test
-style header
//@ <content>
.