1. 4
  1.  

  2. 4

    The code is not in a hot path, and micro-optimizing it is not needed. But still wanted to know what’s faster.

    I should have stopped reading right there :)

    And it resulted in a Go patch of rather dubious real-world use, as noted by the commenters on that PR.

    1. 4

      The part that I found compelling (and the reason I posted it here) was the description of the process that they went through (as a first-time contributor to the compiler) for understanding how the compiler generates optimizations and building a new one.

      1. 2

        True! That’s indeed the good part.