|author||Abhinav Gupta <email@example.com>||Tue Feb 02 14:19:09 2021 -0800|
|committer||GitHub <firstname.lastname@example.org>||Tue Feb 02 14:19:09 2021 -0800|
nomcmp/test: Only set HOME (#84) After some more digging into #83, the issue was actually lack of HOME. We need to specify GOPATH and GOCACHE because we haven't specified a HOME. Given the setup, ``` cd $(mktemp -d) echo "module example.com/demo" > go.mod echo "package demo" > demo.go eval $(gimme 1.16rc1) GO=$(which go) ``` If we run `go build` with an empty environment, it fails as expected. ``` $ env -i $GO build missing $GOPATH ``` Setting HOME gives it a good default place for GOPATH, GOCACHE, and friends. ``` $ env -i HOME=$(pwd)/home $GO build # succeeds ```
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 email@example.com
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.