Re:Google Go: The Good, the Bad, and the Meh
by orangethirty on Monday February 11, 2013 @10:43AM
(#5201319)
Maybe for distribution purposes?
Re:Google Go: The Good, the Bad, and the Meh
by Evbn on Monday February 11, 2013 @10:43AM
(#5201313)
Go run compiled as often each #!python. The runner can cache whatever it wants.
But someone could write shebang-go wrapper to implement this functionality, but a modification to Unix would be needed, since shebang is a magic hack on the '#' character, not configurable,IIRC
So the author wants to type "./foo.go" rather than "go run"? Why not just build your executable, "go build", then you can run/move the resulting executable ./foo.
This really doesn't seem like a big deal / why do I want to compile a utility program every-time I run it?