I don’t understand what you mean by that…I assumed you would understand what I was saying?
There’s far worse options than correct or incorrect hashmaps, there’s collisions. A 50% chance of collision, but also only one bit of data… that’s worse than useless as a hashmap, any practical use of it would be better done in basically any other way
There is no such thing as a ‘terrible hash’, it’s either exact or totally wrong.
HashTag #Octothorpe
I’ve had terrible hash. I’ve also had great hash. So it does exist. /s
You could make a terrible hash brown …
Untrue. There’s far worse outcomes…
It could be 1 bit long
Yeah, about that…
Have you checked my username?
I’ve tried overclocking practically everything under the sun.
Guess what? If you overclock an AGP port from 100MHz to 133MHz, then your GPU might work just fine, but your hard drive gets corrupted.
I don’t understand what you mean by that…I assumed you would understand what I was saying?
There’s far worse options than correct or incorrect hashmaps, there’s collisions. A 50% chance of collision, but also only one bit of data… that’s worse than useless as a hashmap, any practical use of it would be better done in basically any other way
Not sure if this was /s. But outside of hashing in computers , making a hash of something means making it go badly.
CCITT16/CRC32/SHA256/Etc…
Even wrote my own error correction/validation code.
The only /s is the hashtag.