Files
rust/tests/ui
Matthias Krüger 0470728e94 Rollup merge of #132084 - compiler-errors:param-env-with-err, r=lcnr,estebank
Consider param-env candidates even if they have errors

I added this logic in https://github.com/rust-lang/rust/pull/106309, but frankly I don't know why -- the logic was a very large hammer. It seems like recent changes to error tainting has made that no longer necessary.

Ideally we'd rework the way we handle error reporting in all of candidate assembly to be a bit more responsible; we're just suppressing candidates all willy-nilly and it leads to mysterious *other* errors cropping up, like the one that #132082 originally wanted to fix.

**N.B.** This has the side-effect of turning a failed resolution like `where Missing: Sized` into a trivial where clause that matches all types, but also I don't think it really matters?

I'm putting this up as an alternative to #132082, since that PR doesn't address the case when one desugars the APIT into a regular type param.

r? lcnr vibeck
2024-10-24 10:35:40 +02:00
..
2024-07-18 00:00:04 +00:00
2024-10-14 20:24:30 +02:00
2024-08-10 12:07:17 +02:00
2024-08-11 09:58:11 +01:00
2024-09-20 10:02:14 -07:00
2024-10-04 23:38:41 +00:00
2024-04-21 15:43:43 -03:00
2024-09-30 22:21:45 +08:00
2024-08-10 12:07:17 +02: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-09-20 01:20:10 +03:00
2024-09-05 06:37:38 -04:00
2024-06-01 09:40:46 +08:00
2024-09-15 09:51:32 +02:00
2024-07-12 03:22:32 +00:00
2024-09-06 10:32:48 -04:00
2024-09-20 10:02:14 -07:00
2024-04-29 14:53:38 +02:00
2024-08-18 19:46:53 +02:00
2024-05-28 12:31:12 +02:00
2024-09-27 14:40:38 +01:00
2024-10-22 12:55:16 +00:00
2024-08-03 07:57:31 -04:00
2024-09-09 19:39:43 -07:00
2024-10-22 00:03:09 +00:00
2024-10-12 13:01:36 +02:00
2024-10-11 11:30:08 -04:00
2024-10-19 18:07:35 +00:00
2024-10-01 13:55:46 -04:00
2024-06-25 18:06:22 +02: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>.