[swift-evolution] 'Random' Improvements

[Jacob Bandes-Storch]

Directly copying a swift-evolution email I sent almost exactly a year ago:

I encourage anyone thinking about PRNG APIs to check out what C++ STL has
> to offer: http://en.cppreference.com/w/cpp/numeric/random
> And this analysis/extension of it: http://www.pcg-random.org/
> posts/ease-of-use-without-loss-of-power.html



I also found Milos Rankovic's response worth considering:
https://lists.swift.org/pipermail/swift-users/Week-of-Mon-20160404/001676.html

-Jacob

On Wed, Apr 5, 2017 at 10:25 AM, Charlie Monroe via swift-evolution <
swift-evolution at swift.org> wrote:

>
> > On Apr 5, 2017, at 7:00 PM, Peter Dillinger via swift-evolution <
> swift-evolution at swift.org> wrote:
> >
> > Haha:
> >
> >> https://lists.swift.org/pipermail/swift-evolution/Week-of-
> Mon-20170227/033482.html
> >>
> >> In general, I’d recommend against providing a default that we know
> won’t meet everyone’s needs,
> >> as randomness can have security properties.
> >
> > The same could be said of Hashable and even String concatenation, and
> bad randomness isn't even in the OWAP Top 10 (by my reading).
>
> Making some "mistakes" in the past shouldn't encourage to make them in the
> present.
>
> >
> > --
> > Peter Dillinger, Ph.D.
> > Software Engineering Manager, Coverity Analysis, Software Integrity
> Group | Synopsys
> > www.synopsys.com/software
> >
> >
> > _______________________________________________
> > swift-evolution mailing list
> > swift-evolution at swift.org
> > https://lists.swift.org/mailman/listinfo/swift-evolution
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170405/d75fe22b/attachment.html>