Matthias Krüger 00e109f3d4
Rollup merge of #129364 - jswrenn:transmute-layout-errs, r=compiler-errors
safe transmute: gracefully bubble-up layout errors

Changes `.unwrap()`s to `?` to avoid ICEs. Adds ui tests.

Fixes #129327

Tracking Issue: https://github.com/rust-lang/rust/issues/99571

r​? `@compiler-errors`
2024-08-21 21:58:29 +02:00
..
2024-08-13 23:18:31 +02:00
2024-08-17 12:43:25 -04:00
2024-08-17 12:43:25 -04:00
2024-08-18 19:46:53 +02:00
2024-08-18 19:46:53 +02:00
2024-08-17 12:43:25 -04:00
2024-08-18 19:46:53 +02:00
2024-08-18 19:46:53 +02:00
2024-08-17 12:43:25 -04:00
2024-08-18 19:46:53 +02:00
2024-08-17 12:43:25 -04:00
2024-08-17 12:43:25 -04:00
2024-08-16 20:53:13 +01:00
2024-08-18 19:46:53 +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>.