HN

Comments (32)

• 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.[1] https://go-review.googlesource.com/c/go/+/749062[2] https://go-review.googlesource.com/c/go/+/751020
• sbstp
  Go's standard library has always been it's strength, especially the crypto package! Lovely stuff.
• 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
• Hixon10
  Some examples for the upcoming release https://go.dev/doc/go1.27
• 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.
• Menu

  nu2ycombinator
  Those Generics syntax in Golang seems so hard to read.
• theplumber
  This is quite of a big release and I like the new methods on generics.
• lilbigdoot
  This level of generics actually has me interested a bit in Go now.
• Menu

  drivebyhooting
  Can generics be used to improve error handling and eliminate the if err pattern?
• Menu

  kansm
  Tried running a couple of examples in the tour, but ran into a few errors.
• Menu

  stingraycharles
  Am I the only one who’s absolutely shocked that Go finally is embracing generics?Does anyone have a bit of an inside view into what changed in the perspectives of the language maintainers?I’m not buying the “it took us 20 years to understand how to do it correctly” argument, as this is something you explicitly take into consideration when designing the language or not. And it was specifically not a part of language design, and is much harder to retrofit (backwards compatibility).So what changed?
• fang2hou
  [dead]
• okzgn
  [dead]
• Menu

  nothrows
  generics were a slippery slope. give it a decade and Go will be indistinguishable from c++