compiletest: Prepare all simple //@ needs-* conditions in advance#156692
Open
Zalathar wants to merge 3 commits into
Open
compiletest: Prepare all simple //@ needs-* conditions in advance#156692Zalathar wants to merge 3 commits into
//@ needs-* conditions in advance#156692Zalathar wants to merge 3 commits into
Conversation
This intermediate commit makes subsequent diffs/blame a bit nicer, by encouraging git's blame view to preserve line history for the remaining parts of `handle_needs`, which would otherwise be obscured. A subsequent commit will move the list back into `needs.rs` in an altered form.
Collaborator
|
Some changes occurred in src/tools/compiletest cc @jieyouxu
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR makes compiletest check almost all
//@ needs-*conditions in advance, separate from individual tests or directives. The results of these checks are stored in a prepared hashmap that can then be inspected by individual tests when encountering a needs-* directive.This is similar to how
ignore-*/only-*directives work (as of #149470), though currently the two mechanisms don't share code, as they have subtly different requirements.r? jieyouxu