Consistently refer to a test's revision instead of cfg#121373
Merged
bors merged 3 commits intorust-lang:masterfrom Feb 22, 2024
Merged
Consistently refer to a test's revision instead of cfg#121373bors merged 3 commits intorust-lang:masterfrom
revision instead of cfg#121373bors merged 3 commits intorust-lang:masterfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
cfgwithrevision, so that one name is used consistently.