make repeated 'using X ;' a no-op #374
Merged
Conversation
This file contains 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
This change allows putting `using X ;` into build scripts (as opposed to user configs) without creating a conflicting or wrong setup for module X. This is so that build scripts could rely on toolset modules having been configured (at least with default values). The commit only updates toolset modules which allow `using` without arguments in the first place. It also does not change toolset modules for C++ compilers, as nobody does e.g. `using gcc ;` in their build scripts anyway.
grafikrobot
force-pushed
the
fix/modules-init
branch
from
8a09f32
to
1514a75
Compare
grafikrobot
added a commit
that referenced
this pull request
Apr 23, 2024
1 task
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 change allows putting
using X ;into build scripts (as opposed to user configs) without creating a conflicting or wrong setup for module X. This is so that build scripts could rely on toolset modules having been configured (at least with default values).The commit only updates toolset modules which allow
usingwithout arguments in the first place. It also does not change toolset modules for C++ compilers, as nobody does e.g.using gcc ;in their build scripts anyway.Types of changes