The one negative I'd say is that often autovectorisation is 'good enough' and this doesn't really tackle that gap.
While reaching out to CGO is the easier way, it doesn't mean it is the only tool available in Go.
It's being driven by an external contributor who has landed some good changes in the past to the Go compiler. (I think the autovectorization work might be part of their PhD or other academic research, but not sure.)
There's a CL stack here:
It's hard to make predictions with an open source project, but my personal guess is some flavor of it will land (including it is already demonstrating good results without an enormous level of code complexity in the compiler and without overly slowing down compile speeds), but I guess we'll see.
qprofyeh•50m ago
abirch•26m ago
mastermage•20m ago
KeplerBoy•9m ago
pjmlp•11m ago
So yeah, also appreciate have Go in the group instead of manually having to write Assembly.
However not many languages adopt ways to manually write SIMD, because most of us have no idea how to write good SIMD code in first place, I surely don't.