Post

Looks like @golang.org 1.24 is going to be pretty epic! Weak pointers, properly working finalizers alone might change the game! Then optimized maps, native fake clock, benchmarking reliability and ease of use, and tooling dependency management.. and more! antonz.org/go-1-24/

antonz.orgGo 1.24 interactive tourWeak pointers, faster maps, directory-scoped access, and more.

Bryan Boreham

@bboreham.bsky.social

26 Jan 2025

Did you see that reflect2/jsoniter is broken? Hopefully the patch is ok, but I think we have some work to do in Prometheus etc. github.com/golang/go/is...

github.comruntime: jsoniter stack corruption with 32-bit arches, potential GC issues with 64-bit arches · Issue #71408 · golang/goGo version go1.24rc2 linux/amd64 Output of go env in your module/workspace: AR='ar' CC='gcc' CGO_CFLAGS='-O2 -g' CGO_CPPFLAGS='' CGO_CXXFLAGS='-O2 -g' CGO_ENABLED='0' CGO_FFLAGS='-O2 -g' CGO_LDFLAG...

Bartłomiej Płotka

@bwplotka.dev

26 Jan 2025

Wow what an investigation! Sounds like some library was just using runtime internals unsafely 🤔 Curious why that's a Go release blocker (I didn't dive very deep into discussion)

Bryan Boreham

@bboreham.bsky.social

26 Jan 2025

Because they don’t want to spoil our week without taking a minute to think about it. “Just” some library that has 300,000 dependent packages…. Including Kubernetes.

Michael Pratt

@prattmic.com

26 Jan 2025

We take compatibility very seriously. This issue about locking down //go:linkname and covers the rationale. github.com/golang/go/is...

github.comcmd/link: lock down future uses of linkname · Issue #67401 · golang/goOveruse of //go:linkname to reach into Go standard library internals (especially runtime internals) means that when we do change the standard library internals in ways that should not matter, we ca...

Bartłomiej Płotka

@bwplotka.dev

Thanks! Yea this is really generous from Go side, hope users realise that (:

26/1/25, 3:01 pm0 reposts3 likes

No replies yet.