I only instigate panic manually for one thing. Perhaps that will change, but I doubt it.
If I want to send out or write a log to disk then I will call panic rather than os.exit, upon a log.fatal scenario. Think buffered go routine logging. Saving the coder from having to think about it, once initialised. Which produces some ugly output and likely extra processing. Is it possible to call panic in a way that does not kill the process like os.Exit, but without log pollution? I am solely thinking of manually instigated panics, so a noop panic called something like terminate? Or is this bad practice, even when a program is in good operational order when instigated, as the OS is better at cleanup? -- 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/3A8FA632-4991-4245-ABB3-8F4CE1164703%40gmail.com.
