Fix deserialization of check-cfg in config.toml #10799
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.
When improving the check-cfg implementation in #10566 I changed the internal representation of
check_cfg
from multiplebool
options to oneOption<(bool, bool, bool, bool)>
but I didn't realize until rust-lang/rust#82450 (comment) that the internal representation is actually somewhat public as it's used in the[unstable]
in.cargo/config.toml
.And because TOML cannot represent tuples there is no way to set it from the
[unstable]
section. This PR fix this oversight by using a custom deserializer method similar to what was already done forbuild-std
.