Nice patch for #golang bigint:

math/big: make NewInt inlineable and zero allocation
Mark the assembly routines as not escaping their arguments.

https://go-review.googlesource.com/c/go/+/411254/

#golang proposal: add package for using SIMD instructions

https://github.com/golang/go/issues/53171

(Check this too https://github.com/mmcloughlin/avo by @mbmcloughlin 😉)

Hm, friends, what is your use case for SIMD in #golang ?

Yay, #golang performance dashboard https://perf.golang.org/dashboard/

Cool ARM NEON thread.

https://twitter.com/Danlark1/status/1539344279268691970

Scaling our Spreadsheet Engine from Thousands to Billions of Cells in #golang

https://www.causal.app/blog/scaling by @CausalHQ

Go generics are not bad

When programming, we often need to write ‘generic’ functions where the exact data type is not important. For example, you might want to write a simple function that sums up numbers. Go lacked this notion until recently, but it was recently added (as of version 1.18). So I took it out for a spin. In Java, generics work well enough as long as you need “generic” containers (arrays, maps), and as long as stick with functional idioms. But Java will not let me code the way I would prefer. Here is how I would write a function that sums up numbers: int sum(int[] v) { int summer = 0; for(int k = 0; k < v.length; k++) { summer += v[k]; } return summer; } What if I need to support various number types? Then I would like to write the following generic function, but Java won’t let me. // this Java code won't compile static T sum(T[] v) { T summer = 0; for(int k = 0; k < v.length; k++) { summer += v[k]; }…

https://lemire.me/blog/2022/07/08/go-generics-are-not-bad/

Nice #golang proposal by twitter.com/mbmcloughlin is accepted 🎉:
testing: add Elapsed() method to testing.B


https://github.com/golang/go/issues/43620