Auto merge of #14312 - weihanglo:doc, r=epage

docs: clarify `target.'cfg(...)'` doesnt respect cfg from build script
rust-lang · Sep 30, 2024 · dc041a0 · dc041a0
2 parents fe50f67 + 828c7ef
commit dc041a0
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/src/doc/src/reference/config.md b/src/doc/src/reference/config.md
@@ -1173,9 +1173,9 @@ rustflags = ["…", "…"]
 ```
 
 `cfg` values come from those built-in to the compiler (run `rustc --print=cfg`
-to view), values set by [build scripts], and extra `--cfg` flags passed to
-`rustc` (such as those defined in `RUSTFLAGS`). Do not try to match on
-`debug_assertions` or Cargo features like `feature="foo"`.
+to view) and extra `--cfg` flags passed to `rustc` (such as those defined in
+`RUSTFLAGS`). Do not try to match on `debug_assertions`, `test`, Cargo features
+like `feature="foo"`, or values set by [build scripts].
 
 If using a target spec JSON file, the [`<triple>`] value is the filename stem.
 For example `--target foo/bar.json` would match `[target.bar]`.