Files
rust/tests/ui
Guillaume Gomez 4764dceb0f Rollup merge of #124000 - compiler-errors:sugg-tweaks, r=wesleywiser
Use `/* value */` as a placeholder

The expression `value` isn't a valid suggestion; let's use `/* value */` as a placeholder (which is also invalid) since it more clearly signals to the user that they need to fill it in with something meaningful. This parallels the suggestions we have in a couple other places, like arguments.

We could also print the type name instead of `/* value */`, especially if it's suggestable, but I don't care strongly about that.
2024-04-17 00:00:23 +02:00
..
2024-04-15 21:36:52 -04:00
2024-04-07 01:16:45 +02:00
2024-04-15 18:48:12 -04:00
2024-04-14 09:42:53 -04:00
2024-04-12 12:00:14 +02:00
2024-04-12 20:57:07 +00:00
2024-04-03 22:48:55 +01:00
2024-04-15 16:45:48 -04:00
2024-04-12 17:45:15 +01:00
2024-04-15 21:36:52 -04:00
2024-04-07 17:38:07 -03:00
2024-04-15 21:36:52 -04:00
2024-04-15 23:27:22 -04:00
2024-04-11 17:53:27 -04:00
2024-04-07 17:38:07 -03:00
2024-04-14 09:42:53 -04:00
2024-04-11 16:41:41 +00:00
2024-04-11 16:41:41 +00:00
2024-04-09 01:19:43 +02:00
2024-04-07 17:38:07 -03:00
2024-04-06 15:14:16 -04:00
2024-04-04 02:14:57 +01: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>.