From f4c400cdf2e34aa38b7b80ad7da25930379c0ec2 Mon Sep 17 00:00:00 2001 From: Urgau Date: Thu, 25 Apr 2024 00:03:14 +0200 Subject: [PATCH] Add documentation for check-cfg by-default in UI tests --- src/tests/headers.md | 1 + src/tests/ui.md | 3 +++ 2 files changed, 4 insertions(+) diff --git a/src/tests/headers.md b/src/tests/headers.md index 1f2474aa..88a87181 100644 --- a/src/tests/headers.md +++ b/src/tests/headers.md @@ -91,6 +91,7 @@ found in [`header.rs`] from the compiletest source. * [`error-pattern`](ui.md#error-pattern) — errors not on a line * `incremental` — incremental tests not in the incremental test-suite * `no-prefer-dynamic` — don't use `-C prefer-dynamic`, don't build as a dylib + * `no-auto-check-cfg` — disable auto check-cfg (only for `--check-cfg` tests) * `force-host` — build only for the host target * [`revisions`](compiletest.md#revisions) — compile multiple times * [`forbid-output`](compiletest.md#incremental-tests) — incremental cfail rejects output pattern diff --git a/src/tests/ui.md b/src/tests/ui.md index 3f850264..08068235 100644 --- a/src/tests/ui.md +++ b/src/tests/ui.md @@ -361,6 +361,9 @@ multiple `.stderr` files for the different outputs. In the example above, there would be a `.mir.stderr` and `.thir.stderr` file with the different outputs of the different revisions. +> Note: cfg revisions also work inside the source code with `#[cfg]` attributes. +> +> By-convention the `FALSE` cfg is used to have an always false config. ## Controlling pass/fail expectations