bors 164e1297e1 Auto merge of #125610 - oli-obk:define_opaque_types14, r=compiler-errors
Allow constraining opaque types during various unsizing casts

allows unsizing of tuples, arrays and Adts to constraint opaque types in their generic parameters to concrete types on either side of the unsizing cast.

Also allows constraining opaque types during trait object casts that only differ in auto traits or lifetimes.

cc #116652
2024-06-25 05:09:30 +00:00
..
2024-06-12 12:34:47 +00:00
2024-06-19 11:19:25 +05:30
2024-06-21 19:00:18 -04:00
2024-06-24 03:03:34 +08:00
2024-06-21 19:00:18 -04:00
2024-06-24 03:03:34 +08:00
2024-06-05 20:08:00 -04:00
2024-06-20 09:20:45 +00:00
2024-06-07 08:33:58 +00:00
2024-06-21 19:00:18 -04:00
2024-06-21 11:57:24 +00:00
2024-06-21 19:00:18 -04:00
2024-06-21 19:00:18 -04:00
2024-06-16 18:23:48 +02:00
2024-06-20 19:59:27 +08:00
2024-06-22 14:11:11 +00:00
2024-06-17 10:55:42 +00:00
2024-06-21 19:00:18 -04:00
2024-06-12 12:34:47 +00:00
2024-06-21 11:57:24 +00:00
2024-06-19 04:41:56 +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>.