Yura Sokolov <[email protected]> writes: > 2. I don't see why pg_prng_state could not be `typedef uint64 > pg_prng_state[2];`
Please no. That sort of typedef behaves so weirdly that it's
a foot-gun.
regards, tom lane
Yura Sokolov <[email protected]> writes: > 2. I don't see why pg_prng_state could not be `typedef uint64 > pg_prng_state[2];`
Please no. That sort of typedef behaves so weirdly that it's
a foot-gun.
regards, tom lane