Files
rust/tests/ui
bors b6d3be4948 Auto merge of #133436 - nnethercote:rm-NtVis-NtTy, r=petrochenkov
Remove `NtVis` and `NtTy`

The next part of #124141. The first actual remove of `Nonterminal` variants. `NtVis` is a simple case that doesn't get much use, but `NtTy` is more complex.

r? `@petrochenkov`
2025-02-22 06:09:14 +00:00
..
2025-02-20 17:55:31 +00:00
2025-02-13 23:49:09 +01:00
2025-02-21 00:41:17 +00:00
2025-02-21 00:41:17 +00:00
2025-02-21 00:26:30 +01:00
2025-02-21 00:41:17 +00:00
2025-02-14 00:37:23 +01:00
2025-02-21 00:41:17 +00:00
2025-02-21 00:41:17 +00:00
2024-12-31 23:46:39 +08:00
2025-02-14 00:37:23 +01:00
2025-02-21 00:41:17 +00:00
2025-02-07 16:02:19 +00:00
2025-02-21 15:49:46 +11:00
2025-02-21 00:41:17 +00:00
2025-01-28 19:35:51 +00:00
2025-02-21 00:41:17 +00:00
2025-01-07 16:04:14 +01:00
2025-01-26 13:55:59 +00:00
2025-02-18 16:22:16 +00:00
2025-01-30 20:37:56 -07:00
2025-02-21 00:41:17 +00:00
2025-02-21 00:41:17 +00:00
2025-02-21 00:41:17 +00:00
2025-02-13 23:49:09 +01:00
2025-02-21 00:41:17 +00:00
2025-02-21 00:41:17 +00:00
2025-01-29 15:45:13 +00:00
2024-12-25 10:36:32 +01:00
2025-01-23 10:55:01 +00:00
2025-02-04 21:42:43 +05:30

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 interpret a test.

As part of an ongoing 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 a legacy compiletest-style test header. To fix this, you should migrate to the ui_test-style header //@ <content>.