Go 1.27 Interactive Tour: Generic Methods, UUIDs, and Post-Quantum Security
I am continuing the interactive tour series for Go 1.27, showcasing hands-on examples of new features like generic methods and struct literal field selectors. This guide covers generalized function type inference, faster memory allocation, and improved goroutine debugging with labels and leak profiles. We also explore the new standard library uuid package and post-quantum signature support in crypto/mldsa, offering a practical look at what changes for developers.
A leaked goroutine is one blocked forever on a channel, mutex, or similar, with no way to ever make progress.
- baalimago
This: "(b Box[T]) Map[U any](f func(T) U) Box[U]" is the type of cognitive weight I was happy that Go avoided.
- chenxiaolong
This release also fixes runtime.findnull() to be compatible with MTE on Android ([1] and [2]). This was the only thing preventing MTE from being enabled for apps that use gomobile on MTE-compatible Android OS's like GrapheneOS.
- mappu
Automatically draining http response bodies is a risky silent behaviour change. I think it will be an improvement for most applications, but it's very subtle if you were relying on the old behaviour
- my-next-account
>The quieter but bigger change
I really wish they didn't use such stupid LLM-isms.
- sbstp
Go's standard library has always been it's strength, especially the crypto package! Lovely stuff.
- nu2ycombinator
Those Generics syntax in Golang seems so hard to read.
- mayama
Adding simd in std and even being used in map is nice. Would have to look for places to experiment with it in hot loops in code I have.
- Altern4tiveAcc
>func (b Box[T]) Map[U any](f func(T) U) Box[U] {}
That's completely unreadable.