bors 7042c269c1 Auto merge of #125645 - RalfJung:unclear_local_imports, r=nnethercote
add unqualified_local_imports lint

This lint helps deal with https://github.com/rust-lang/rustfmt/issues/4709 by having the compiler detect imports of local items that are not syntactically distinguishable from imports from other cates. Making them  syntactically distinguishable ensures rustfmt can consistently apply the desired import grouping.
2024-09-23 19:27:33 +00:00
..
2024-09-21 13:05:21 +02:00
2024-09-22 10:46:59 -04:00
2024-09-20 09:18:47 +00:00
2024-09-20 10:02:14 -07:00
2024-03-06 12:01:54 +00:00
2024-09-20 10:02:14 -07:00
2024-09-12 08:08:38 +02:00
2024-09-15 09:51:32 +02:00
2024-09-20 10:02:14 -07:00
2024-09-20 10:02:14 -07:00
2024-09-23 11:57:28 +02:00
2024-09-09 19:39:43 -07:00
2024-09-18 16:45:48 -04:00
2023-01-11 09:32:08 +00:00
2023-03-08 00:00:18 +00:00
2023-01-11 09:32:08 +00:00
2023-01-11 09:32:08 +00:00
2023-01-11 09:32:08 +00: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>.