-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
double support scientific notation. #2079
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! It is better to add a test to get the value.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this contribution.
IMO. Integers are also deserved to support such notation.
1E10 is supposed to be regard as integer or double? The format is rarely used. |
Codecov Report
@@ Coverage Diff @@
## master #2079 +/- ##
==========================================
- Coverage 86.90% 86.80% -0.10%
==========================================
Files 636 639 +3
Lines 59819 61130 +1311
==========================================
+ Hits 51984 53066 +1082
- Misses 7835 8064 +229
Continue to review full report at Codecov.
|
I think it's a double, such as the |
doc done |
Co-authored-by: trippli <trippli@tencent.com> Co-authored-by: dutor <440396+dutor@users.noreply.github.com>
* drop space not exist * return when key not found Co-authored-by: pengwei.song <90180021+pengweisong@users.noreply.github.com>
Parser can deal with scientific notation like 123.456E1.