Go 1.22's go/types Alias type shows the challenge of API compatibility
The iterator proposal is a neat way to write “lazy loops”, where we never generate more results than we actually use. Let’s see what that would look like in Go programs.
While I like Go’s approach of treating errors as values as much as the next person, it inevitably leads to a situation where there isn’t a one-size-fits-all strategy for error handling like in Python or JavaScript. The usual way of dealing with errors entails returnin...
While I like Go’s approach of treating errors as values as much as the next person, it inevitably leads to a situation where there isn’t a one-size-fits-all strategy for error handling like in Python or JavaScript. The usual way of dealing with errors entails returnin...
While I like Go’s approach of treating errors as values as much as the next person, it inevitably leads to a situation where there isn’t a one-size-fits-all strategy for error handling like in Python or JavaScript. The usual way of dealing with errors entails returnin...
Learn how to build custom error types in Go to create stack traces without runtime overhead, inspired by Rob Pike's Upspin error handling.
I was on episode 302 of the Go Time podcast, talking about What’s New in Go 1.22. Check it out!
The Microsoft builds of the Go patches released today, Feb 6, are now available for download. The post Go 1.21.7-1 and 1.20.14-1 Microsoft builds now available appeared first on Microsoft for Go Developers.
Go 1.22 enhances for loops, brings new standard library functionality and improves performance.
#494 — February 6, 2024 Unsub | Web Version Go Weekly Testing Out Profile-Guided Optimization on Dolt's SQL Benchmarks — Profile-guided optimization was introduced in Go 1.20. The Dolters(?) created a benchmark and saw small (t...