Disallow tuple variants with incorrect order of #[serde(default)] attributes
#2561
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
Mingun
force-pushed
the
tuple-variant-default-check
branch
from
5740423
to
aadc690
Compare
…ributes (review this commit with "ignore whitespace changes" option on)
Mingun
force-pushed
the
tuple-variant-default-check
branch
from
aadc690
to
96d9034
Compare
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.
Continuation of work from #2553, but expanded to tuple variants.
Actually, we should also disallow using
#[serde(default)]on elements of newtype structs and newtype variants, but this is highly coupled with skip problems, so I wait before the relevant PRs will be merged