Files
rust/tests/ui
bors 4bc39f028d Auto merge of #120924 - xFrednet:rfc-2383-stabilization-party, r=Urgau,blyxyas
Let's `#[expect]` some lints: Stabilize `lint_reasons` (RFC 2383)

Let's give this another try! The [previous stabilization attempt](https://github.com/rust-lang/rust/pull/99063) was stalled by some unresolved questions. These have been discussed in a [lang team](https://github.com/rust-lang/lang-team/issues/191) meeting. The last open question, regarding the semantics of the `#[expect]` attribute was decided on in https://github.com/rust-lang/rust/issues/115980

I've just updated the [stabilization report](https://github.com/rust-lang/rust/issues/54503#issuecomment-1179563964) with the discussed questions and decisions. Luckily, the decision is inline with the current implementation.

This hopefully covers everything. Let's hope that the CI will be green like the spring.

fixes #115980
fixes #54503

---

r? `@wesleywiser`

Tacking Issue: https://github.com/rust-lang/rust/issues/54503
Stabilization Report: https://github.com/rust-lang/rust/issues/54503#issuecomment-1179563964
Documentation Update: https://github.com/rust-lang/reference/pull/1237

<!--
For Clippy:

changelog: [`allow_attributes`]: Is now available on stable, since the `lint_reasons` feature was stabilized
changelog: [`allow_attributes_without_reason`]: Is now available on stable, since the `lint_reasons` feature was stabilized
-->

---

Roses are red,
Violets are blue,
Let's expect lints,
With reason clues
2024-06-26 16:38:30 +00:00
..
2024-05-02 19:42:31 -04:00
2024-06-25 17:22:22 +02:00
2024-06-19 11:19:25 +05:30
2024-06-21 19:00:18 -04:00
2024-04-21 15:43:43 -03:00
2024-06-25 17:22:22 +02:00
2024-03-06 12:01:54 +00:00
2024-04-21 15:43:43 -03:00
2024-06-25 17:22:22 +02:00
2024-04-14 21:34:14 +05:30
2024-04-12 20:57:07 +00:00
2024-06-05 20:08:00 -04:00
2024-06-20 09:20:45 +00:00
2024-06-01 09:40:46 +08:00
2024-06-07 08:33:58 +00:00
2024-06-21 19:00:18 -04:00
2024-06-21 11:57:24 +00:00
2024-06-21 19:00:18 -04:00
2024-04-29 14:53:38 +02:00
2024-04-25 10:47:24 +08:00
2024-05-20 11:13:10 -04:00
2024-04-07 17:38:07 -03:00
2024-06-21 19:00:18 -04:00
2024-06-16 18:23:48 +02:00
2024-05-28 12:31:12 +02:00
2024-04-11 17:53:27 -04:00
2024-04-21 15:43:43 -03:00
2024-06-20 19:59:27 +08:00
2024-06-22 14:11:11 +00:00
2024-02-29 14:43:43 +01:00
2024-06-17 10:55:42 +00:00
2024-04-27 10:54:31 +03:00
2024-06-21 19:00:18 -04:00
2024-03-15 13:37:41 +00:00
2024-06-12 12:34:47 +00:00
2024-06-21 11:57:24 +00:00
2024-05-21 20:16:39 +00:00
2024-04-27 10:54:31 +03:00
2024-06-19 04:41:56 +00:00
2024-02-22 18:05:28 +00:00
2024-02-07 10:42:01 +08:00
2024-06-25 18:06:22 +02:00
2024-02-07 10:42:01 +08:00

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>.