Files
rust/tests/ui
Matthias Krüger 457087ed29 Rollup merge of #131549 - compiler-errors:try-in-sync, r=spastorino
Add a note for `?` on a `impl Future<Output = Result<..>>` in sync function

It's confusing to `?` a future of a result in a sync function. We have a suggestion to `.await` it if we're in an async function, but not a sync function. Note that this is the case for sync functions, at least.

Let's be a bit more vague about a fix, since it's somewhat context dependent. For example, you could block on it, or you could make your function asynchronous. 🤷
2024-10-22 15:28:41 +02: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-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-09-15 09:51:32 +02:00
2024-09-06 10:32:48 -04:00
2024-09-20 10:02:14 -07:00
2024-08-18 19:46:53 +02:00
2024-09-27 14:40:38 +01:00
2024-10-04 23:38:41 +00: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-09-26 13:21:15 +02:00
2024-10-19 18:07:35 +00:00
2024-10-01 13:55:46 -04:00
2024-10-01 13:55:46 -04:00
2024-09-18 16:45:48 -04: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>.