On Friday, 4 November 2016 22:49:17 UTC-4, Nate Finch wrote:
>
> If the script you run with go run returns a non-zero exit status, go run
> prints "exit status N" and itself then returns with exit code 1.
>
> Now, this seems like a double mistake - first off, the only time go run
> should print anything out is if it had some problem actually running the
> code, i.e. unable to find the file, unable to compile, etc. After that, it
> should just directly mirror whatever the running code writes to stdout and
> stderr, no more no less. This also means that if the script returns exit
> code 13, go run should return with exit code 13. Right now it only ever
> returns 0 for success and 1 for an error.
>
> Is this something that can be changed? Not sure how backwards
> compatibility is handled in these situations.
>
It does seem a little bit arbitrary and contrary to UNIX tool design
principles. It's unlikely that this is a compatibility concern for anyone.
File a bug if you feel strongly about it.
--
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.
