On Tuesday, 7 November 2017 22:22:43 UTC+11, Vladimir Varankin wrote: > > Thank you, Dave, for the response. > > > You’ll have a more enjoyable go experience if you structure your code > into packages and use go build or preferably go install. > > To be fair, I don't think that having the ability to do build + run in one > go command goes against the fact that it's worth to write code in a proper > modular way. And I don't see how splitting "main" package into several > files goes against it as well. > > It feels there is nothing wrong with the idea of making "go run" more than > a command that one should never use in a real project. >
Have you tried go run dir/*.go ? That should work well enough. > > Regarding the use of "go build/install", could you talk more, what > benefits do they provide for the development process. I only aware of > incremental builds, that speed up the compilation time, which, in my > experience, isn't that bad for a small/middle size daemons. > sure, i wrote about it a while ago here, https://dave.cheney.net/2014/06/04/what-does-go-build-build > > > On Tuesday, November 7, 2017 at 1:21:52 PM UTC+3, Dave Cheney wrote: >> >> 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 Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
