Repository navigation
mkStdGen should take a Word64 instead of an Int #141
Description
Activity
This is because
mkStdGenprecedes use of splitmix (since 1.2). But you can use generator from splitmix directly. And it exposes construction fromWord64Why not just expose the Word64 seeding function directly? ...
If backwards compat is the issue, I suggest mkStdGenW64 :: Word64 -> StdGen (maybe I'll provide a PR myself?)Yeah, we are not about to break compatibility of a function that is like 3 decades old. However, I do agree that providing
mkStdGen64 :: Word64 -> StdGenwould be a good idea. It would be great if you could submit a PR? Side note, I don't think suffixWis necessary)I'd like to very explicitly provide 64 bits.
I am sure you know this, but just to make sure we are on the same page. By casting
InttoWord64you are not loosing any bits, unless you are on a 32bit machine- added 2 commits that reference this issue
on Nov 26, 2023 Great to see this closed! Quality.
I want to deterministically seed with
mkStdGenbased on some unique bits I have (some UUID). I noticed thatmkStdGentakeIntand thenfromIntegrals it to aWord64, which splitmix actually uses.Why not just expose the
Word64seeding function directly? I'd like to very explicitly provide 64 bits.For now, I can either just do my stuff in
Word32/Word64andfromIntegralmyself. Or I can do bit stuff and dosplitbinary search.If backwards compat is the issue, I suggest
mkStdGenW64 :: Word64 -> StdGen(maybe I'll provide a PR myself?)