[email protected] randomSeeded gives different results for some seeds vs 0.1.1

[lionel-rowe]

Describe the bug

[email protected] randomSeeded gives different results for some seeds (not covered by current tests). cc @kt3k

Steps to Reproduce

for (const v of ['0.1.0', '0.1.1']) {
    const { randomSeeded } = await import(`jsr:@std/random@${v}`)
    const seed = 6552010792480112863n
    console.log(`${v}: ${randomSeeded(seed)()}`)
}

Expected

0.1.0: 0.6705842935480177
0.1.1: 0.6705842935480177

Actual

0.1.0: 0.6705842935480177
0.1.1: 0.10435933456756175

If the seed is 6552010792480112862n instead of 6552010792480112863n, the results are the same.

The 0.1.0 results are consistent with rust rand.

Environment

[email protected]

[lionel-rowe]

Cause: increment was being ORed with 1 upon setting only in the constructor, not when it was used to move away from initial value prior to being initialized.