Add recursive data cost to fuzzer + speed up deserialize_any
identifier check
#506
+35
−20
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.
Adding layers, e.g. enum variants or tuples, is not without cost in the format, so let's enforce that in the fuzzer as well.
Checking for an identifier in
deserialize_any
previously used theidentifier
parser, which has complex error handling to produce nice error messages. Since we only need to check if one is there, we now useskip_identifier
, which now returnsOption<&str>
instead ofbool
, and thus avoids any allocation in the check.* [ ] I've included my change inCHANGELOG.md