Matthias Krüger e713b2a00c
Rollup merge of #125416 - compiler-errors:param-env-missing-copy, r=lcnr
Use correct param-env in `MissingCopyImplementations`

We shouldn't assume the param-env is empty for this lint, since although we check the struct has no parameters, there still may be trivial where-clauses.

fixes #125394
2024-05-23 14:09:25 +02:00
..
2024-05-13 16:55:58 -04:00
2024-05-21 20:16:39 +00:00
2024-05-20 11:13:10 -04:00
2024-05-20 19:21:30 -04:00
2024-05-21 20:16:39 +00:00
2024-05-20 20:30:44 +02:00
2024-05-20 11:13:10 -04:00
2024-05-19 19:10:04 +02:00
2024-05-17 18:33:37 -03:00
2024-05-22 22:40:34 +02:00
2024-05-20 11:13:10 -04:00
2024-05-18 18:11:20 -07:00
2024-05-20 20:30:44 +02:00
2024-05-21 20:16:39 +00:00
2024-05-22 22:40:34 +02:00
2024-05-21 20:16:39 +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>.