with these data. If the goroutine panics (assume I am calling a poorly
written third-party package), what is the Go way of recovering and
restarting the goroutine? In my particular case, loss of data is acceptable
(i.e., dropping the input which caused the panic). Are there any issues
with having the goroutine restart itself inside a defer/recover (see
playground link below)?
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 email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.