Thanks Davis, I think it's a good idea. I started with an interface (for
the whole array) but it was too cumbersome.
As for the build tags, do you know of a good reference, specially for this
use case.
@Roberts, it's hard to give exact numbers, specially for the heap since
it's been a long proces
I’m curious if you have any benchmarks or branches of the code prior to the
assembly code and off heap memory management. This seems like an ideal case to
test if things like that are worth the effort ?
> On Dec 12, 2018, at 9:59 AM, 'David Chase' via golang-nuts
> wrote:
>
> Before you have
Before you have too many people depending on the current interfaces, would
you consider replacing the point encoding of even/odd array elements with,
say, "type Point struct { x, y float64}" ? I think it would be a more
attractive interface.
Would also be nice to use build tags to allow use of
