Files
rust/tests/ui
Matthias Krüger ae92125a75 Rollup merge of #127574 - lcnr:coherence-check-supertrait, r=compiler-errors
elaborate unknowable goals

A reimplemented version of #124532 affecting only the new solver. Always trying to prove super traits ends up causing a fatal overflow error in diesel, so we cannot land this in the old solver.

The following test currently does not pass coherence:
```rust
trait Super {}
trait Sub<T>: Super {}

trait Overlap<T> {}
impl<T, U: Sub<T>> Overlap<T> for U {}
impl<T> Overlap<T> for () {}

fn main() {}
```

We check whether `(): Sub<?t>` holds. This stalls with ambiguity as downstream crates may add an impl for `(): Sub<Local>`. However, its super trait bound `(): Super` cannot be implemented downstream, so this one is known not to hold.

By trying to prove that all the super bounds of a trait before adding a coherence unknowable candidate, this compiles. This is necessary to prevent breakage from enabling `-Znext-solver=coherence` (#121848), see tests/ui/coherence/super-traits/super-trait-knowable-2.rs for more details. The idea is that while there may be an impl of the trait itself we don't know about, if we're able to prove that a super trait is definitely not implemented, then that impl would also never apply/not be well-formed.

This approach is different from #124532 as it allows tests/ui/coherence/super-traits/super-trait-knowable-3.rs to compile. The approach in #124532 only elaborating the root obligations while this approach tries it for all unknowable trait goals.

r? `@compiler-errors`
2024-07-30 04:31:54 +02:00
..
2024-07-28 03:11:54 +08:00
2024-07-12 11:52:04 -04:00
2024-05-02 19:42:31 -04:00
2024-07-18 00:00:04 +00:00
2024-07-14 13:50:09 +09:00
2024-07-18 14:32:10 +02:00
2024-07-19 23:27:42 +03:00
2024-04-21 15:43:43 -03:00
2024-07-06 14:24:20 +02:00
2024-07-02 02:30:38 +01:00
2024-07-29 17:50:12 +01:00
2024-04-12 20:57:07 +00:00
2024-07-24 21:03:27 +00:00
2024-06-01 09:40:46 +08:00
2024-06-21 19:00:18 -04:00
2024-07-24 21:03:27 +00:00
2024-07-12 03:22:32 +00:00
2024-04-29 14:53:38 +02:00
2024-05-20 11:13:10 -04:00
2024-07-21 21:42:10 +08:00
2024-04-07 17:38:07 -03:00
2024-07-29 17:50:12 +01:00
2024-05-28 12:31:12 +02:00
2024-07-24 08:46:52 +02:00
2024-04-11 17:53:27 -04:00
2024-07-24 21:03:27 +00:00
2024-07-22 22:51:53 +00:00
2024-07-24 21:03:27 +00:00
2024-05-21 20:16:39 +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>.