the whole gobin / gopath thing was annoying as a beginner: I just want to build this module and use that local module
go build ./... Goes where ?
go build ./... Goes where ?
go test ./… tests all files in the project, so I assume build does something similar.
> When compiling multiple packages or a single non-main package, build compiles the packages but discards the resulting object, serving only as a check that the packages can be built.
From https://pkg.go.dev/cmd/go#hdr-Compile_packages_and_dependenc...
A bit annoying when you want to build a bunch of executables, but it's not something I need often and it's easy to script.
go build -o some/dir/ ./...
will actually output the binaries