SplittableRandom update

Martin Buchholz martinrb at google.com
Fri Sep 20 15:34:51 UTC 2013

On Fri, Sep 20, 2013 at 8:25 AM, Kasper Nielsen <kasperni at gmail.com> wrote:

> Hi,
> This is minor, but I hate it when bounds check does not include the
> specified parameters.
> Makes it much harder to track down a bug, if all you have is a stack trace.

I agree.  My own Best Practice is to write

         if (!(bound > 0.0))
            throw new IllegalArgumentException(badBound(bound));

(I'm still waiting for VMs to take care of the out-lining of cold code

More information about the core-libs-dev mailing list