* 'Bryan Mills' via golang-nuts <golang-nuts@googlegroups.com> [180402 15:10]: > This is indeed a subtle pattern, but it's not clear to me how often it > comes up in practice, and preventing deferred function calls from blocking > could result in all kinds of other unwanted side effects.
I'd like to point out that the problem is not specific to defer during panic; the exact same problem can occur when executing deferred code during a normal return. It is also the same as putting an infinite loop somewhere else that you did not intend (i.e. not in a defer). I don't think the language spec (or implementation) needs to have any special safeguard for an unintended infinite loop just because it happens during deferred code while panicking. ...Marvin -- 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.
