-
Notifications
You must be signed in to change notification settings - Fork 407
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
Add choose methods for both Java and Scala BigDecimal. #670
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
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
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.
It's less explicit, but couldn't the user just specify the minimum desired scale on either of the parameters for
high
andlow
to theGen.choose
method? For example,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 also came up in the discussion in #637, but I didn't conclude that there's a justification for the
minScale
parameter to theChoose
factory.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.
You could accomplish this by just changing this line in your pr:
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.
I don't understand what that last line accomplishes, the LHS (
low.scale max high.scale
) will always be chosen over the RHS (low.scale min high.scale
).My experience here is that many people using
BigDecimal
don't necessarily think about scale. For example, code likeGen.choose(BigDecimal(0), BigDecimal(1))
will only produce two possible values, but this issue won't necessarily be detected by authors, leading to unexpectedly weak tests.Using the implicit scale in
BigDecimal
has tripped people up, especially given how tricky it is to reason about. For example, authors might think thatGen.choose(BigDecimal(0.0000), BigDecimal(1.0000))
will give them a scale of 4, but actually it will be 1 due to a different treatment ofString
andDouble
constructors:I'm open to simplifying the API a bit but I strongly feel like we should have a relatively rigorous
minScale
, even if it's hardcoded. It's possible to truncate a generatedBigDecimal
for less precision but the reverse is not possible, so I feel like more precision (to a point) is a better default.