You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been analyzing // +build usage in the Go ecosystem and turned up internal/cpu/init.go, which says:
// +build 386 !gccgo,amd64 !gccgo,amd64p32 !gccgo
It looks like the intent here was "(386 && !gccgo) || (amd64 && !gccgo) || (amd64p32 && !gccgo)",
but the meaning is "386 || (!gccgo && amd64) || (!gccgo && amd64p32) || !gccgo",
or equivalently "386 || !gccgo".
There are two ways to write the presumed intent. As one line:
// +build 386,!gccgo amd64,!gccgo amd64p32,!gccgo
or as two lines:
// +build 386 amd64 amd64p32
// +build !gccgo
Best,
Russ
The text was updated successfully, but these errors were encountered:
I've been analyzing // +build usage in the Go ecosystem and turned up internal/cpu/init.go, which says:
It looks like the intent here was "(386 && !gccgo) || (amd64 && !gccgo) || (amd64p32 && !gccgo)",
but the meaning is "386 || (!gccgo && amd64) || (!gccgo && amd64p32) || !gccgo",
or equivalently "386 || !gccgo".
There are two ways to write the presumed intent. As one line:
or as two lines:
Best,
Russ
The text was updated successfully, but these errors were encountered: