You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was looking over the docs for Using recently, and noticed that ControlThrowable suppresses NonFatal exceptions. But I don't think that should be the case. ControlThrowable is control-flow, and ought to lose to "something went wrong".
Currently, exceptions are ranked using this method in which all NonFatal exceptions are ranked lower than fatal exceptions, and the various fatal exceptions are ranked relative to each other. ControlThrowable is already suppressed in favour of any other fatal exception; I simply propose it be suppressed in favour of all other exceptions.
While this does change behaviour potentially underneath users' feet, I think it is still a worthwhile change because:
ControlThrowable (usually non-local return) isn't that common
the current behaviour essentially silently drops exceptions
I don't know if anyone has ever encountered this situation anyway
The text was updated successfully, but these errors were encountered:
SethTisue
changed the title
Incorrect/unreasonable suppresion behavior of s.u.Using
Incorrect/unreasonable suppression behavior of s.u.UsingFeb 20, 2025
I was looking over the docs for
Using
recently, and noticed thatControlThrowable
suppressesNonFatal
exceptions. But I don't think that should be the case.ControlThrowable
is control-flow, and ought to lose to "something went wrong".Currently, exceptions are ranked using this method in which all
NonFatal
exceptions are ranked lower than fatal exceptions, and the various fatal exceptions are ranked relative to each other.ControlThrowable
is already suppressed in favour of any other fatal exception; I simply propose it be suppressed in favour of all other exceptions.While this does change behaviour potentially underneath users' feet, I think it is still a worthwhile change because:
ControlThrowable
(usually non-localreturn
) isn't that commonThe text was updated successfully, but these errors were encountered: