It probably was for platform independence since the any system that has a /dev/urandom will use that as a source of entropy anyway [0]. If you know you'll be on a system with that and need more than one goroutine to use a random stream you probably should just open it yourself so that goroutines dont have to serialize their access. Although, I dont know what the system does to provide urandom so concurrent reads might not really work for that anyway. Seems like it'd be simple to test out if you're curious enough.

[0] https://golang.org/src/crypto/rand/rand_unix.go

You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 13 of 15 | next ›
Discussion Overview
groupgolang-nuts @
postedSep 1, '13 at 6:24p
activeJan 6, '15 at 9:38a



site design / logo © 2022 Grokbase