-
Notifications
You must be signed in to change notification settings - Fork 432
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
Rename thread_rng
to ThreadRng::new()
?
#404
Comments
I do not support this. Calling
|
I don't share that sentiment,
It is doing a lot of work if it is the first call in the thread.
That is my point, right now we are inconsistent. |
I wouldn't remove |
Having both will just lead to pointless style wars. |
I agree that we shouldn't simply have See also this point about replacing In any case, I think we should postpone these ideas until after the 0.5 release. |
Since there do appear to be quite a few people who watch this repository and this is mostly style, can I get some more opinions on this, i.e. do you prefer writing Either way, we already have the |
There is almost no interest on this, so I guess we can just forget it. |
This would be more consistent with
OsRng
,EntropyRng
,JitterRng
,ReseedingRng
andBlockRng
.The text was updated successfully, but these errors were encountered: