Lazy initialization in Go using atomics
Aside from the main performance guide, I'm considering using the blog to share quick, informal insights and quirks related to Go performance and optimizations. Let's see if this casual experiment survives contact with reality.
Someone recently pointed out that my getResource() function using atomics has a race condition. Guilty as charged—rookie mistake, really. The issue? I naïvely set the initialized flag to true before the actual resource is ready. Brilliant move, right? This means that with concurrent calls, one goroutine might proudly claim victory while handing out a half-baked resource:
var initialized atomic.Bool
var resource *MyResource
func getResource() *MyResource {
if !initialized.Load() {
if initialized.CompareAndSwap(false, true) {
resource = expensiveInit()
}
}
return resource
}