-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
seq: zero gets padded if specified with scientific notation #6926
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
Labels
Comments
I would like to work on this issue if it's not already being handled. |
sure :) |
aimerlief
added a commit
to aimerlief/coreutils
that referenced
this issue
Dec 7, 2024
- Updated the parse_exponent_no_decimal function to treat 0e... as zero. - Added test cases to verify correct behavior for 0e15 and -w 0e15. Fix: uutils#6926
aimerlief
added a commit
to aimerlief/coreutils
that referenced
this issue
Dec 7, 2024
- Updated the parse_exponent_no_decimal function to treat 0e... as zero. - Added test cases to verify correct behavior for 0e15 and -w 0e15. Fix: uutils#6926
aimerlief
added a commit
to aimerlief/coreutils
that referenced
this issue
Dec 7, 2024
- Updated the parse_exponent_no_decimal function to treat 0e... as zero. - Added test cases to verify correct behavior for 0e15 and -w 0e15. Fix: uutils#6926
cakebaker
pushed a commit
that referenced
this issue
Dec 7, 2024
* fix(seq): handle 0e... scientific notation without padding - Updated the parse_exponent_no_decimal function to treat 0e... as zero. - Added test cases to verify correct behavior for 0e15 and -w 0e15. Fix: #6926 * fix(seq): improved parse for accurate BigDecimal handling * apply missing cargo fmt formatting adjustments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I noticed that if I specify zero with scientific notation (and without specifying
-w
), the zero gets padded. With GNUseq
, there is no padding:The text was updated successfully, but these errors were encountered: