Files
rust/tests/ui
bors 9d28fe3976 Auto merge of #139000 - compiler-errors:rigid-missing-item, r=lcnr
Rigidly project missing item due to guaranteed impossible sized predicate

This is a somewhat involved change, but it amounts to treating missing impl items due to guaranteed impossible where clauses (dyn/str/slice sized, cc #135480) as *rigid projections* rather than projecting to an error term, since that was preventing either reporting a proper error (in an empty param env) *or* successfully type checking the code (in the presence of trivially false where clauses).

Fixes https://github.com/rust-lang/rust/issues/138970

r? `@lcnr` `@oli-obk`
2025-04-10 04:03:59 +00:00
..
2025-03-03 08:52:07 +01:00
2025-04-06 21:41:47 +02:00
2025-02-27 10:26:33 +00:00
2024-12-12 23:36:27 +00:00
2025-03-11 20:26:10 -07:00
2025-02-24 18:48:40 +00:00
2024-12-12 23:36:27 +00:00
2025-01-28 19:35:51 +00:00
2025-03-29 08:10:15 +01:00
2025-02-27 20:02:25 +00:00
2025-03-30 01:32:21 +03:00
2025-04-04 09:44:19 +02:00
2025-03-11 20:26:10 -07:00
2025-01-29 15:45:13 +00:00
2025-03-27 14:11:11 +01:00
2025-02-27 10:26:33 +00:00
2025-01-23 10:55:01 +00:00
2025-02-04 21:42:43 +05:30
2024-12-02 03:43:50 -07:00
2025-04-04 16:32:18 +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 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>.