Fix ..Default::default()
for struct Config
#911
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.
Previously the
depfile
option added a new private member to theConfig
struct - a breaking change which many users complained about. Making the field public, but hiding it from the documentation and excluding it fromserde
reverts the breakage, while keeping the depfile functionality.I also considered adding an
InternalConfig
struct, but this would require breaking changes to at leastConfig::from_file()
andConfig::from_root_or_default()
, which is a lot more invasive than my PR.Closes #908