Making these immutable will be a real pain as demonstrated by the over-dispersed exponential example. In particular, to maintain performance, it would require that all constructors be arranged to allow injection of a random number generator. Management of that would be a nasty code issue. Better to just allow the parameters to be changed so that a user can ignore the issue of which PRNG is used.
On Sat, Mar 6, 2010 at 7:32 AM, Phil Steitz <phil.ste...@gmail.com> wrote: > This is a separate issue, as you point out. I am +1 on deprecating > the setters so these all become immutable in 3.0. > -- Ted Dunning, CTO DeepDyve
