-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception catching mode. #165
Comments
How is it going with this? Meanwhile I made a small test program which checks how it works with both signals and observables. The results are more scary than I thought. If any signal handler / observable binding throws an exception, not only this prevents other handlers / bindings from being called with the current signal / state change, but none of the handlers/bindings ever run again on further signals / state changes. |
P.S. Adding exception handling to Otherwise I think the changes proposed in the issue description would be good to have ASAP :) |
Via e.g.
-D tink_core.catch_exceptions
a few try/catch barriers would be added:Callback.guardStackoverflow
(which is where almost all dispatching goes through) any exceptions would be caught and reported, as well as all other places that call user code (e.g.CallbackLink.cancel
).Error.oncaught((e.Exception)->Void)
where user can add errors reporters (if none are added, useconsole.error
on JS and the closest possible thing on other platforms).The text was updated successfully, but these errors were encountered: