4 ms·

Does that prevent, or more expose?

• klodolph 5y ago
  I think the general idea is "shift left" which you can say exposes bugs earlier, or prevents bugs from reaching production, which is kind of a "six dozen of one, half dozen of the other". Bugs which are exposed early enough do not get committed. "Shift left" just means that you shift the feedback to the developer farther left in the build process, closer (in time and space) to when the mistake was made.
• EE84M3i 5y ago
  I don't know about go specifically, but many languages randomize their hash tables to avoid Hash Collision DoS attacks. This is a problem for any piece of software putting attacker-controlled data into a hash-table that does not randomize the hashing and where they assume that it will be amortized constant time.
  • masklinn 5y ago
    Go does have that, but it also specifically and explicitly randomises iteration order.
    • EE84M3i 5y ago
      Is that a separate implementation?
      • masklinn 5y ago
        No, it’s the builtin hashmap. It had a random seed for the hash to avoid collision predictability but it also, separately has a shuffled iteration order for maps.