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

DM-12995/RFC-436: Random: ensure seed is non-zero #309

Merged
merged 1 commit into from Jan 26, 2018

Conversation

PaulPrice
Copy link
Contributor

Random has accepted a seed value of zero and then thrown an exception.
This is not necessary, since we can construct a seed value that is
non-zero from whatever we're given.

@PaulPrice PaulPrice force-pushed the tickets/DM-12995 branch 3 times, most recently from b9976d5 to 0d1685e Compare January 16, 2018 18:16
Copy link
Member

@TallJimbo TallJimbo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Just to confirm my own sanity, this implementation matches @ktlim's proposal on RFC-436, and hence differs from your original plan?

@PaulPrice PaulPrice force-pushed the tickets/DM-12995 branch 3 times, most recently from 8b0cf77 to b085c63 Compare January 23, 2018 00:20
@PaulPrice
Copy link
Contributor Author

Correct, I have abandoned my original (stupid) plan and embraced @ktlim's sensible method.

Random has accepted a seed value of zero and then thrown an exception.
This is not necessary, since we can simply use a non-zero seed value.
@PaulPrice PaulPrice merged commit bf7488d into master Jan 26, 2018
@ktlim ktlim deleted the tickets/DM-12995 branch August 25, 2018 06:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants