Files
rust/tests/ui
Matthias Krüger b2d132f10e Rollup merge of #116863 - workingjubilee:non-exhaustive-is-not-ffi-unsafe, r=jieyouxu
warn less about non-exhaustive in ffi

Bindgen allows generating `#[non_exhaustive] #[repr(u32)]` enums. This results in nonintuitive nonlocal `improper_ctypes` warnings, even when the types are otherwise perfectly valid in C.

Adjust for actual tooling expectations by avoiding warning on simple enums with only unit variants.

Closes https://github.com/rust-lang/rust/issues/116831
2024-10-19 22:00:54 +02:00
..
2024-10-04 23:38:41 +00:00
2024-09-30 22:21:45 +08:00
2024-10-11 11:30:08 -04:00
2024-10-15 20:42:17 -04:00
2024-10-15 20:42:17 -04:00
2024-10-17 20:43:31 +02:00
2024-10-17 00:16:19 +08:00
2024-09-27 14:40:38 +01:00
2024-10-04 23:38:41 +00:00
2024-10-12 13:01:36 +02:00
2024-10-11 11:30:08 -04:00
2024-09-26 13:21:15 +02:00
2024-10-01 13:55:46 -04:00
2024-10-01 13:55:46 -04:00
2024-10-07 14:45:49 -07: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>.