Alternative draft of big number extensions #249
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
…rtly based on work done by gappleto97 in msgpack#248.
Author
|
I just created my own (probably over-engineered) draft covering big integers, high precision floating point numbers, and fractions - please discuss: #249 Different to #248 by @gappleto97, I used different extension types for different things - thus, allowing do discuss the different aspects (big integers, high precision floats, fractions) separately, and also to add only selected ones to the spec. |
markusschaber
changed the title
modify fractions section, replace bignum with specific types
|
This proposal does not specify the binary format of the payload: two's compliment, signed magnitude, or one's compliment. Most arbitrary-precision integer libraries use signed magnitude. If signed magnitude were to be used, then the sign must appear somewhere in the message frame. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 discussed in #206. Partly based on work done by gappleto97 in #248.