Allow hexadecimal number format convention parsing #551
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
nitzancarmi
force-pushed
the
hex_prefix_support
branch
4 times, most recently
from
fb874d6
to
16cacc8
Compare
Allow parsing of the hexadecimal number standard format (e.g. `0x<number>`). Signed-off-by: Nitzan Carmi <nitzanc@mellanox.com>
nitzancarmi
force-pushed
the
hex_prefix_support
branch
from
16cacc8
to
3d4ad9f
Compare
|
1, Standard json do not support octal and hexadecimal number. |
|
Sorry, this is totally out of the spec we're aiming for (RFC 7159), and not even in the newer one (RFC 8259), so I don't expect that we'll merge this. |
|
Alright then. Tnx! |
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.
Allow parsing of the hexadecimal number standard
format (e.g.
0x<number>).Signed-off-by: Nitzan Carmi nitzanc@mellanox.com