add support for encoding int64-buffer#22
Open
rochdev wants to merge 1 commit into
Open
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 PR adds support for encoding actual 64bit integers instead of the maximum of 53bit supported natively by JavaScript. It does so by detecting that the value is an int64-buffer object. This is the same library that is used by msgpack-lite to support 64bit integers.
Right now the change is limited to encoding since decoding would require adding
int64-bufferas a dependency, which is a change that should likely be discussed, and might have to be added as a configuration option. I also only added support for big endian right now since decoding always uses big endian. This might be configured as well, but it might be enough to support only big endian.