about summary refs log tree commit diff
path: root/compiler/rustc_pattern_analysis/src
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2024-02-21 22:48:58 +0100
committerGitHub <noreply@github.com>2024-02-21 22:48:58 +0100
commit084e2322f34f81bf1f50d4a77d8b8add9c0e95f0 (patch)
tree7ba5b62999ecb9c7f59ba07ae84c3add863b7fb6 /compiler/rustc_pattern_analysis/src
parent718998591ef2e4fc159fe3ef666a1b05ef0a1585 (diff)
parent544d09132bef3d483a0e10b4bb25e25079107e37 (diff)
downloadrust-084e2322f34f81bf1f50d4a77d8b8add9c0e95f0.tar.gz
rust-084e2322f34f81bf1f50d4a77d8b8add9c0e95f0.zip
Rollup merge of #121373 - Zalathar:test-revision, r=oli-obk
Consistently refer to a test's `revision` instead of `cfg`

Compiletest allows a test file to specify multiple “revisions” (`//@ revisions: foo bar`), with each revision running as a separate test, and having the ability to define revision-specific headers (`//`@[foo]` ignore-blah`) and revision-specific code (`#[cfg(foo)]`).

The code that implements this feature sometimes uses the term “cfg” instead of “revision”. This results in two confusingly-different names for the same concept, one of which is ambiguous with other kinds of configuration (such as compiletest's own config).

This PR replaces those occurrences of `cfg` with `revision`, so that one name is used consistently.
Diffstat (limited to 'compiler/rustc_pattern_analysis/src')
0 files changed, 0 insertions, 0 deletions