Skip to content
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 #77

Open
gene-pavlovsky opened this issue Oct 3, 2022 · 1 comment
Open

Exception catching mode #77

gene-pavlovsky opened this issue Oct 3, 2022 · 1 comment

Comments

@gene-pavlovsky
Copy link
Member

The issue is the same as in the tink_core ticket: haxetink/tink_core#165
Or will adding an exception catching mode to tink_core also fulfill the same purpose for tink_state?

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.

exception-test.tar.gz

@gene-pavlovsky
Copy link
Member Author

I reckon this kind of solution should fix the observables issue as well: haxetink/tink_core#175

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant