Understanding Go Error Types: Pointer vs. Value| Fillmore Labs Blog
An in-depth guide to programming with assertions and advocating for the use of assertions at work, based on ~6 years of experience spread out across a variety of codebases.| typesanitizer.com
本文永久链接 - https://tonybai.com/2023/02/19/how-to-determine-if-two-interface-vars-are-equal 近日一位《Go语言第一课》专栏的读者向我提出一个问题，代码如下： func main() { printNonEmptyInterfa| tonybai.com
Go Wiki: LoopvarExperiment| go.dev
TL;DR ¶ Some of the wisdom contained in Josh Bloch’s Effective Java book is relevant to Go. panic and recover are best reserved for exceptional circumstances. Reliance on panic and recover can noticeably slow down execution, incurs heap allocations, and precludes inlining. Internal handling of failure cases via panic and recover is tolerable and sometimes beneficial. Abusing Java exceptions for control flow ¶ Even though my Java days are long gone and Go has been my language of predilecti...| jub0bs.com
This is a discussion about a new syntax that may be used to handle errors. This is issue #71203 converted into a discussion. I've written a tool that converts ordinary Go code into code that uses t...| GitHub
As I will be switching clients next year, I will also be switching programming languages, from Go …| Brain Baking
Most programming language ecosystems provide assert functions in their testing libraries but not Go's. Go's standard testing package follows a more direct and to-the-point approach.| henvic.dev
jorge started as a Go learning project, so writing down my thoughts on the language seemed like a good way to wrap up this devlog.| jorge
Proposal: Less Error-Prone Loop Variable Scoping| go.googlesource.com
Go Modules Reference| go.dev
How and when to use Go maps.| go.dev
Documentation| go.dev
Go 1.21 shipped a preview of a change in Go 1.22 to make for loops less error-prone.| go.dev
Learn how to substitute a ternary operator not available in Go| gosamples.dev
A variable's name is more important than its type, so the name should be more prominent and come first in declarations.| benhoyt.com
An introduction to Go errors.| go.dev
If you write any code that deals with manual memory management, you are likely familiar with the concept of a “use after free” bug. These bugs can be the source of, at best, program crashes, and at worst serious vulnerabilities. A lesser discussed counterpart to use after free, is “use after return”. In some cases, the latter can be even more troublesome, due to the operations that are performed when one procedure calls another.| danielmangum.com
I’ve namedropped contracts enough here that I think it’s finally time to go talk about them. A lot of people conflate them with class interfaces / dynamic typing / “your unit tests are your contract”, which muddies the discussion and makes it hard to show their benefits. So I’d like to build up the idea of contracts from first principles. We’re going to work in Python, up until the point where things get crazy.| Hillel Wayne