News for hackers. Stuff that matters.
Re:Conc: Better Structured Concurrency for Go by yakaccount4 on Thursday January 12, 2023 @10:00PM (#34363461)
There seems to not be any standard list of unrecoverable panics/aborts, but this Stackoverflow post [1] has a list of a few.

As far as the user/developers are concerned, it doesn't matter too much, since you have no option to recover them, but it would be nice if it was explained if defers are still ran. I'm assuming they are not.

1. https://stackoverflow.com/questions/57486620/are-all-runtime...

Re:Conc: Better Structured Concurrency for Go by preseinger on Thursday January 12, 2023 @10:14PM (#34363545)
If there is no way for callers to reliably distinguish recoverable panics from unrecoverable panics, then this distinction doesn't really exist, does it? Panics are panics.
Re:Conc: Better Structured Concurrency for Go by yakaccount4 on Thursday January 12, 2023 @10:32PM (#34363639)
I'm not sure what point you are trying to make anymore.

Of course you cannot distinguish between unrecoverable and recoverable panics, because by definition an unrecoverable panic is not recoverable. There is no caller to distinguish between it - it is killed.

Re:Conc: Better Structured Concurrency for Go by preseinger on Friday January 13, 2023 @12:43AM (#34364358)
Oh. You're using the word panic to describe a superset of actual panics and other even more serious errors. Those things you call unrecoverable panics are not actually panics.

The point I'm trying to make is that panics are not errors by another name, and they are not safe to recover from in general.