On Wednesday, April 15, 2020 at 1:02:47 PM UTC-4, Marvin Renich wrote: > > In the Go tour, what is the purpose of requiring the user to explicitly > press the "Kill" button when the build fails? This seems completely > unnecessary to me. > > If this is just a natural consequence of the internal implementation, it > would, in my opinion, be well worth the effort to make a failed build > exit without requiring the user to press "Kill". > > ...Marvin > > As far as I can tell, you do not ever need to hit 'kill'. If the build (compile) fails, then it exists immediately. If the program gets into an infinite loop, or otherwise takes too long, it will eventually exit with the message:
timeout running programProgram exited: status 255. It looks to me like the kill button is there in case you create a long running program and do not wish to wait for the timeout. Are you seeing different behavior? If so it may be a bug. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/77efb0a1-d9da-41cc-8f00-d2161d00d283%40googlegroups.com.
