|author||Abhinav Gupta <firstname.lastname@example.org>||Thu May 14 15:34:20 2020 -0700|
|committer||Abhinav Gupta <email@example.com>||Fri May 15 15:47:25 2020 -0700|
Separate files for each atomic type As in #73, separate each atomic type into its own file to ease review of transition to generated code. After moving every atomic to its own file, the atomic.go file serves only as documentation, so rename it to doc.go.
Simple wrappers for primitive types to enforce atomic access.
$ go get -u go.uber.org/atomic@v1
As of v1.5.0, the import path
go.uber.org/atomic is the only supported way of using this package. If you are using Go modules, this package will fail to compile with the legacy import path path
We recommend migrating your code to the new import path but if you're unable to do so, or if your dependencies are still using the old import path, you will have to add a
replace directive to your
go.mod file downgrading the legacy import path to an older version.
replace github.com/uber-go/atomic => github.com/uber-go/atomic v1.4.0
You can do so automatically by running the following command.
$ go mod edit -replace firstname.lastname@example.org
The standard library‘s
sync/atomic is powerful, but it’s easy to forget which variables must be accessed atomically.
go.uber.org/atomic preserves all the functionality of the standard library, but wraps the primitive types to provide a safer, more convenient API.
var atom atomic.Uint32 atom.Store(42) atom.Sub(2) atom.CAS(40, 11)
See the documentation for a complete API specification.
Released under the MIT License.