Go
-
[ On | No ] syntactic support for error handling
One of the oldest and most persistent complaints about Go concerns the verbosity of error handling. We are all intimately (some may say painfully) familiar with this code pattern: The test if err != nil can be so pervasive that it drowns out the rest of the code. This typically happens in programs that do a lot
-
More predictable benchmarking with testing.B.Loop
Go developers who have written benchmarks using the testing package might have encountered some of its various pitfalls. Go 1.24 introduces a new way to write benchmarks that’s just as easy to use, but at the same time far more robust: testing.B.Loop. Traditionally, Go benchmarks are written using a loop from 0 to b.N: Using b.Loop instead is a trivial change: