-
Notifications
You must be signed in to change notification settings - Fork 33
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
Make Display for Decimal more human-friendly #477
Merged
Merged
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
e4c3d5d
Make Display for Decimal more human-friendly
jobarr-amzn de86c80
Update src/types/decimal.rs
jobarr-amzn bb418a5
Update src/types/decimal.rs
jobarr-amzn bd82ad8
PR feedback and skip rustfmt
jobarr-amzn 9925c62
WIDE_NUMBER as usize
jobarr-amzn File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
This could be a
usize
, which would allow you to skip:len as i64
down on line 308WIDE_NUMBER as usize
on line 314There 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.
Yeah
WIDE_NUMBER
should be ausize
.len as i64
on line 308 thendot_index
gets inferred asusize
, but that's not right becausedot_index
should be able to be negative.WIDE_NUMBER as usize
on line 314 to agree withlen
or castWIDE_NUMBER as i64
on line 324 for easiest comparison with the negative-valueddot_index
there. The latter is the right call becauseWIDE_NUMBER
should be ausize
.Unless I'm missing something, which is probable :) I'd also happily take feedback or second opinions on the
WIDE_NUMBER
concept- whether we ought to have it at all, whether it ought to be applied "evenly" on both whole and fractional numbers, and how large it should be.