Matthias Krüger 6f5765599e
Rollup merge of #126018 - nnethercote:rm-box_pointers-lint, r=lcnr
Remove the `box_pointers` lint.

As the comment says, this lint "is mostly historical, and not particularly useful". It's not worth keeping it around.

r? ``@estebank``
2024-06-30 18:25:31 +02:00
..
2024-06-25 17:22:22 +02:00
2024-06-21 19:00:18 -04:00
2024-06-28 10:57:35 +00:00
2024-06-27 15:19:08 -04:00
2024-06-25 17:22:22 +02:00
2024-06-25 23:43:19 +02: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-27 15:19:08 -04:00
2024-06-20 19:59:27 +08:00
2024-06-28 15:44:20 +00:00
2024-06-28 10:57:35 +00:00
2024-06-26 17:41:24 +03:00
2024-06-21 19:00:18 -04:00
2024-06-27 15:19:08 -04:00
2024-06-21 11:57:24 +00:00
2024-06-25 18:06:22 +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>.