-
Notifications
You must be signed in to change notification settings - Fork 16
Added discard remaining input option when deserializing #13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
gfusee
wants to merge
1
commit into
zefchain:main
Choose a base branch
from
gfusee:feature/deserialize_discarding_bytes
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wouldn't use
unsafefor that. I believe what you're asking is a variant where we don't callend(). Or equivalently exposing theDeserializerstruct. Historically, @bmwill and I have pushed back on this idea. Not sure if there is a stronger argument now.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was inspired by some std's methods that are marked as unsafe even they don't use any unsafe code, such as
Vec::set_lenTo not call
endwould indeed achieve what I'm asking. However,endis defined in a trait (BcsDeserializer), which implicitly tells that it will be called anyway at the... end of something? Even the comment states this:The Deserializer::end method should be called after a type has been fully deserialized.It would be unintuitive to not call it in my opinion.Exposing the
Deserializeris a solution, but it would oblige developers to write themself the code to bypass theendfunction. What do you think about a variant of this where:endfunction to be a requirement of theBcsDeserializertrait, which has no side effect since it is never called in a generic context (at least I didn't find any generic usage, correct me if I'm wrong)Deserializerstruct toRawDeserializer, and we remove theendmethodDefaultDeserializerthat has the end method that ensures if there is no remaining input. It usesRawDeserializerlogic behind the sceneDefaultDeserializerwhereDeserializerwas usedDefaultDeserializerandRawDeserializerfrom_bytes_discarding_remaining_input, nonew_discarding_remaining_inputand nodiscard_remaining_inputThis way the developer would not notice any change, but someone wanting to not have the checks would just have to use
RawDeserializerdirectlyLet me know if it looks good for you 🙏