If you want to understand more about what happens to exceptions in `asyncdispatch` \- where they're raised, where they're caught (or not), etc, I'd recommend reading <https://github.com/status-im/nim-chronos/pull/166> which provides an overview for the analogous problem in chronos, and a first step towards a solution - there are more steps planned though.
- nim-ws - websockets for Nim treeform
- nim-ws - websockets for Nim arnetheduck
- nim-ws - websockets for Nim Araq
- nim-ws - websockets for Nim arnetheduck
- nim-ws - websockets for Nim enthus1ast
- nim-ws - websockets for Nim arnetheduck
- nim-ws - websockets for Nim dom96
- nim-ws - websockets for Nim arnetheduck
- nim-ws - websockets for Nim dom96
- nim-ws - websockets for Nim arnetheduck
- nim-ws - websockets for Nim arnetheduck
- nim-ws - websockets for Nim dom96
- nim-ws - websockets for Nim arnetheduck
- nim-ws - websockets for Nim mildred
- nim-ws - websockets for Nim Araq
- nim-ws - websockets for Nim alexeypetrushin
- nim-ws - websockets for Nim Araq
