1. 22
  1.  

  2. 3

    You might consider putting some basic benchmark comparisons in the README.

    1. 1

      Thanks for the suggestion! We added some :)

      1. 1

        Sweet!

    2. 2

      Talking about CPU-friendly code, is there a good example of a Go application written in a data-oriented design paradigm? Something that Mike Acton and Stoyan Nikolov described in their talks concerning C++.

      1. 6

        go-geom uses a linear layout for its coordinates, which makes it 30% faster than the equivalent C library in benchmarks, see https://github.com/twpayne/go-geom/blob/master/INTERNALS.md#efficient.