Fix incorrect count of fields passed to tuple deserialization methods #2466
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 count should mean the number of fields expected in the serialized form, so if some fields are skipped, they shouldn't be counted.
Methods affected:
After this PR number of fields passed to deserializer methods will be the same as number, passed to the serializer methods.
I didn't include tests in that PR, because correct test suite should cover all possible situations, and many of them have certain problems. I plan to include a full testsuite in my upcoming PR for fixing #2105.
Right now you can see what changed in the generated code by running the following commands:
test_suite/tests
folder and change its extension to.rs
...\serde\test_suite> cargo expand --all-features --test skip