Eugene Kabanov
Eugene Kabanov
Just some comments from your example: You should know that ``` proc myProc() {.async: raises: [].} ``` is not equal to ``` proc myProc() {.async.} ``` In first case procedure...
Why do you need `Result` here? How you handle `ref CatchableError` errors? Is there any examples on this template usage?
But `{.async: (raises: []).}` means that it will **NOT** "bubbleCancellation" because it will not raise `CancelledError`, while `{.async: (raises: [CancelledError]).}` means that it will "bubbleCancellation".
> store callbacks in linked list, so multiple parties can wait for future completion (this doesn't affect performance, first item of the linked list can be inlined into struct). callback=...
@andreaferretti if we are talking about `asynchttpserver` (for example), most of the time there at least 2 callbacks registered. It looks like * recv(1) sets callback(1). * In frame context...
Ok, maybe its my mistake i have talked about callbacks inside of dispatcher, not about callbacks inside of `Future`.
AVX is faster than AVX2 because of data size... AVX2 implementation uses AVX implementation for 64 bytes data.
It doesn't matter where we used `129` - we should change this number to any number which is < 128.
There was time, when Nim Compiler was mangled types and identifiers with simple numbers, right now only unique identifiers are mangled with simple numbers, but type identifiers got mangling like...
The problem is not in `unittest2`, because last example is impossible to reproduce for me, but initial one is possible to reproduce on Linux and Windows with Nim 1.6.18.