Stuart Cook 517e7ce37f
Rollup merge of #130311 - heiseish:issue-70849-fix, r=fmease
(fix) conflicting negative impl marker

## Context

This MR fixes the error message for conflicting negative trait impls by adding the corresponding the polarity marker to the trait name.

## Issues

- closes #70849

r​? `@fmease`
2024-09-14 20:22:41 +10:00
..
2024-08-28 23:32:40 +01:00
2024-09-03 09:19:29 +02:00
2024-09-13 02:43:49 +08:00
2024-08-28 23:32:40 +01:00
2024-09-05 06:37:38 -04:00
2024-09-09 19:39:43 -07:00
2024-09-06 10:32:48 -04:00
2024-09-09 19:39:43 -07:00
2024-09-09 19:39:43 -07:00
2024-09-09 19:39:43 -07:00
2024-08-31 23:56:45 +02:00
2024-09-03 14:36:21 +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>.