Fix is_flag_supported not respecting emit_rerun_if_env_changed (#1147)#1148
Merged
NobodyXu merged 1 commit intorust-lang:mainfrom Jul 12, 2024
Merged
Fix is_flag_supported not respecting emit_rerun_if_env_changed (#1147)#1148NobodyXu merged 1 commit intorust-lang:mainfrom
NobodyXu merged 1 commit intorust-lang:mainfrom
Conversation
Is there some way to do a |
Contributor
That will end up with too many configurations inherited, better start afresh and assign what's needed. |
Merged
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.
When I add a Cargo override to the example from #1147:
Then the extra
rerun-if-env-changeddirectives go away (except for one that's maybe a separate small bug):I'm not sure how to add a unit test for this, since it doesn't look like
emit_rerun_if_env_changedis currently tested.It also seems like it's pretty easy to write more bugs like this, since anytime a feature is added to
Buildwe need to remember to come to these lines and think about whether it should be inherited. I'm not sure how to make that better though. Thoughts?