9a420c6b05
it seems that due to a naming conflict from asyncdispatch, callSoon is deduced to raise exceptions even if it doesn't in modules that import both, even indirectly - this patch randomly works around the issue with some more overloads |
||
|---|---|---|
| .. | ||
| streams | ||
| transports | ||
| asyncfutures2.nim | ||
| asyncloop.nim | ||
| asyncmacro2.nim | ||
| asyncsync.nim | ||
| debugutils.nim | ||
| handles.nim | ||
| sendfile.nim | ||
| srcloc.nim | ||
| timer.nim | ||
| transport.nim | ||