Files
rust/tests/ui
Matthias Krüger 5bceee4762 Rollup merge of #129154 - wafarm:fix-95463, r=estebank
Fix wrong source location for some incorrect macro definitions

Fixes #95463

Currently the code will consume the next token tree after `var` when trying to parse `$var:some_type` even when it's not a `:` (e.g. a `$` when input is `($foo $bar:tt) => {}`). Additionally it will return the wrong span when it's not a `:`.

This PR fixes these problems.
2024-08-16 19:58:59 +02:00
..
2024-07-28 03:11:54 +08:00
2024-08-13 23:18:31 +02:00
2024-07-29 21:47:19 -04:00
2024-08-16 09:07:55 +10:00
2024-07-18 00:00:04 +00:00
2024-08-10 12:07:17 +02:00
2024-07-18 14:32:10 +02:00
2024-07-19 23:27:42 +03:00
2024-08-10 12:07:17 +02:00
2024-08-09 22:02:23 -04:00
2024-08-10 12:07:17 +02:00
2024-08-02 11:34:54 +00:00
2024-08-02 11:34:54 +00:00
2024-08-08 00:41:39 +08:00
2024-07-12 03:22:32 +00:00
2024-07-21 21:42:10 +08:00
2024-08-10 12:07:17 +02:00
2024-08-02 11:34:54 +00:00
2024-08-13 23:00:42 +02:00
2024-08-12 13:00:12 +10:00
2024-08-02 11:34:54 +00:00
2024-08-03 07:57:31 -04:00
2024-08-10 12:07:17 +02:00
2024-07-24 21:03:27 +00:00
2024-07-22 22:51:53 +00:00
2024-08-10 12:07:17 +02: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>.