Real talk: go run is for examples as large as one would type into the
playground. Nothing more.
You’ll have a more enjoyable go experience if you structure your code into
packages and use go build or preferably go install.
--
You received this message because you are subscribed to the Google
Currently `go run` accepts a file or a list of ".go" files:
```
% go help run
usage: go run [build flags] [-exec xprog] gofiles... [arguments...]
```
For me, it doesn't seem to be obvious, why can't "go run" accept the
directory that contains files of the main package as an input?
Note, I'm awa