bors e875391458 Auto merge of #123812 - compiler-errors:additional-fixes, r=fmease
Follow-up fixes to `report_return_mismatched_types`

Some renames, simplifications, fixes, etc. Follow-ups to #123804. I don't think it totally disentangles this code, but it does remove some of the worst offenders on the "I am so confused" scale (e.g. `get_node_fn_decl`).
2024-05-21 08:06:41 +00:00
..
2024-05-13 16:55:58 -04:00
2024-05-20 11:13:10 -04:00
2024-05-20 11:13:10 -04:00
2024-05-17 18:33:37 -03:00
2024-05-20 11:13:10 -04:00
2024-05-20 20:30:44 +02:00
2024-05-20 11:13:10 -04:00
2024-05-08 21:37:54 +02:00
2024-05-19 19:10:04 +02:00
2024-05-17 18:33:37 -03:00
2024-05-20 11:13:10 -04:00
2024-05-16 21:10:07 +08:00
2024-05-20 11:13:10 -04:00
2024-05-20 20:30:44 +02:00
2024-05-20 20:57:14 +00:00
2024-05-08 21:37:55 +02:00
2024-05-17 18:33:37 -03:00
2024-05-20 11:13:10 -04: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>.