Currently, the thread macro's behavior when an exception occurs is to print the exception (with println), and swallow it.
Although I make a habit of wrapping a try around code inside a thread form, I still find this a bit limited; it would be nice if there was a function that could be dynamically bound, that handled the case of an exception inside a thread.
Environment
0.1.278.0-76b25b-alpha
Activity
Show:
Alex Miller November 18, 2021 at 10:13 PM
I think the uncaught exception handler mechanism is now available for this, so closing this ticket. If there is a more specific use case where that's prohibitive, feel free to file a more specific problem.
Alex Miller August 6, 2014 at 4:29 PM
Patches on ASYNC-76 have been applied and exceptions will now flow up to the top of the thread, where they can be caught by the standard Thread uncaught exception handler mechanism or ultimately by the default uncaught exception handler, which can be set for the application. There may still be further changes to support exception handling in thread/go.
Currently, the thread macro's behavior when an exception occurs is to print the exception (with
println), and swallow it.Although I make a habit of wrapping a
tryaround code inside athreadform, I still find this a bit limited; it would be nice if there was a function that could be dynamically bound, that handled the case of an exception inside athread.