Skip to content
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

number parsing #993

Closed
Yaossg opened this issue Mar 4, 2018 · 2 comments
Closed

number parsing #993

Yaossg opened this issue Mar 4, 2018 · 2 comments
Labels
solution: wontfix the issue will not be fixed (either it is impossible or deemed out of scope)

Comments

@Yaossg
Copy link

Yaossg commented Mar 4, 2018

Bug Report

number literals like "+1"_json , ".5"_json , "5."_json are invalid

Feature Request

hexadecimal floating literal (like0x1.2p3)

@nlohmann
Copy link
Owner

nlohmann commented Mar 4, 2018

All these numbers are non-confirming JSON, see

numbers

@nlohmann
Copy link
Owner

nlohmann commented Mar 5, 2018

We shall not add features that do not conform to JSON.

@nlohmann nlohmann closed this as completed Mar 5, 2018
@nlohmann nlohmann added the solution: wontfix the issue will not be fixed (either it is impossible or deemed out of scope) label Mar 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solution: wontfix the issue will not be fixed (either it is impossible or deemed out of scope)
Projects
None yet
Development

No branches or pull requests

2 participants