[Computer-go] fast + good RNG

[Kahn Jonas]

> I just think Go (except trivial implementation cases) should be very
> insensitive to RNGs.  It is not like many Monte Carlo applications where
> you just call the RNG in a tight loop in regular manner to move in the
> same state space.  In a Go program, you call the RNG from playouts in
> all sorts of irregular cases to pick out of available patterns
> /liberties/neighbor groups, to check whether to apply a given
> heuristic, and the set of moves to pick from shift-shapes continuously.
> Even with a short-period RNG, you always use that number to decide
> something else.
>
> One of these times, I'll check if Pachi can still play Go with RNG
> being (seed += 1313) % max.

You're right, a simple LCG is probably more than sufficient.

Jonas