RE: computer-go: Sharing Go modules

["Grajdeanu, Adrian" <adrian.grajdeanu@xxxxxxx>]

My take is biased towards C++, but I guess it doesn't have to be limited to
C++. I follow the generic programming model and such I have a struct named
coord that encodes the coordinates somehow. In most of the cases I don't
care how the coords are encoded, just that passing it as an argument is easy
(32 bits). Then I can start off with an implementation that is not very fast
(like needing to multiply by 19 every time I need to index the board) and
further down the line, if this turns out to be the bottleneck, I can change
it to something more efficient. Can't all these algorithms that we're trying
to share be written such that they don't care how the data is stored?

While I could propose something for C++ along these lines, I don't think I
am the best to propose it for Java. What do you guys think? Any takes?
Volunteers?