-
-
Notifications
You must be signed in to change notification settings - Fork 147
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
Unhandled promise #106
Comments
While sometimes useful, it could also be unhelpful in other situations. Imagine situations where something is fetched and the promise is resolved with an object, but that object provides access to further promise operations, which are executed eagerly, so there might be no interest in these promises at all, whether they succeed or fail. What's your suggestion to mark these as "not interested"? |
Unhanded promise rejection in asynchronous programing is same as uncaught exception in synchronous programming. Is there any "not interested" for
In JavaScript we have same solution . see https://stackoverflow.com/questions/31472439/catch-all-unhandled-javascript-promise-rejections |
I'm planning of introducing something like this in the future, see also #87. |
Closing as duplicate of #87. |
I think it's good that we have a method like
set_exception_handler
for promise that sets a user-defined unhandled promise rejection handler functionThe text was updated successfully, but these errors were encountered: