[WIP]explicit support for uint vs int in simple serialize #114
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
p-mc2
changed the title
p-mc2
changed the title
|
Seems like my implementation is the best way to handle this in ssz but there are a ton of spots where there's overflow because things that should be unsigned are named 'int64' for example. Should I go through and edit all of these ints to uints or am I misunderstanding something? Thanks. |
|
I think if we move forward with |
|
closing this one |
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.
As has been discussed, it's probably worth our time to explicitly support uint vs int in simple serialize to avoid confusion. Thanks.