toolset.using preserves current project #407
Merged
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.
Proposed changes
using
project rule preserves the current project, andtoolset.using
does not. The problem is that the former is not available in modules that are not projects, and so one has to preserve the current project manually, just in case. I don't think there is ever any point in not preserving the current project when initialising a toolset module, so this change pushes this reponsibility ontoolset.using
.Types of changes
Checklist