✅ Random help
How do I get a random ulong out of Random.Next()? Random.NextInt64() seems to actually only give a random 63-bit number
ECast it...?
Ei meant how do i get out a fully random 64 bit number
Ei can obviously cast it
Eand then cast that to ulong?
ENo?
EYou'd need long.MinValue as the min
EThe 64th bit is the sign
Eahhh okok
Ei think i can do that
Ei can cast that to ulong right
Ethis would work right
CYeah, that should work. (I'd use
long.MinValue and long.MaxValue)Ethat's why i have the type cast there
E...then what is that point
Ethat would turn -1 into 1
Ewhich leaves me with the same 63 bits worth of numbers
Ewell then what does Math.Abs do
KNextInt64 return a non-negative long
https://learn.microsoft.com/en-us/dotnet/api/system.random.nextint64?view=net-9.0
https://learn.microsoft.com/en-us/dotnet/api/system.random.nextint64?view=net-9.0
EToo slow
Ethere is an override
E*overload
Ethis will take any int64, inclusive of negative ones
EI'd possibly wrap the cast in
uncheckedEah yea
Eooo ok
Eit seems to be working without that tho
Esee
Eok that's settled
CIt will throw if you're in a
checked context, either because someone wrapped your method in checked, or if the assembly was compiled with checked arithmeticEoh
Eso slap unchecked on it gotchu
Eyes
CYeah, it's one of those things that normally doesn't matter, but is good practice just for the odd case where it does matter for some reason
C... Why?
Ei need the number that comes out to be fixed
Ei seeded the random
C(That also doesn't have a method for Int64's, FWIW)
Eit's ok the Random.NextInt64() works
Ejust gotta tweak it a lil
CI don't understand how
RandomNumberGenerator makes it any easier to generate a random ulong ><CI don't know how you determined that he needed a cryptographically secure random number from that discussion 
Ause the
Span<byte> overload, then reinterpret cast to ulong with Unsafe.AsA@ElectricTortoise
Eit's ok i have an easier solution already
Ewhy not just
Unsafe.BitCast<long, ulong> ?CWhy use Unsafe when you can just use a normal cast?
Efair
Ait's been established that it's positive, it's missing a bit of information
Aand the span overload is more flexible, if you know what you're doing
Alike if you're going to need 100 numbers, you can
stackalloc a buffer for all of them and generate them all at once