Skip to content

Clarify gen_weighted_bool behaviour #282

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

Merged
merged 1 commit into from
Mar 4, 2018

Conversation

pitdicker
Copy link
Contributor

Although we don't know the future of gen_weighted_bool yet, a bit of clarifying documentation can't hurt I think? See also #47.

@dhardy
Copy link
Member

dhardy commented Mar 4, 2018

It would probably be correct to panic if n == 0, but never mind. Not sure how much this is used; I suppose it is good enough where it is though.

@dhardy dhardy merged commit 8245d5f into rust-random:master Mar 4, 2018
@pitdicker pitdicker deleted the gen_weighted_bool_doc branch March 22, 2018 10:14
pitdicker pushed a commit that referenced this pull request Apr 4, 2018
Clarify `gen_weighted_bool` behaviour
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.

2 participants