Thank you for the explanation,
This makes sense - I only wanted to bring it up in the (unlikely) case
it was an oversight.
My thinking was that there might be a potential use case of something like:
private static final SecureRandom shared_source = new
SecureRandom(); // thread safe sour
From Guy:
You are right that the comment in the JEP was a little loose, and that the
implementation(s) of the split/splits methods could in principle draw random
values from a RandomGenerator that is not itself splittable. There might even
be applications for such functionality.
However, we ch
just wanted to add that the JEP says: "SplittableRandomGenerator extends
RandomGenerator and also provides
methods named split and splits. Splittability allows the user to spawn a
new RandomGenerator from an existing RandomGenerator that will generally
produce statistically independent results."
