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."
which adds to my suspicion that this might be a api bug.
-michael
On 13.07.21 14:45, Michael Bien wrote:
Hello,
i was wondering if SplittableGenerator.split(SplittableGenerator
source) is missing out on a potential usecase when the source itself
is not splittable. The implementation looks like it only requires
basic calls which could be also provided by the RandomGenerator
interface as source.
best regards,
michael