Eugene Kabanov

Its very easy to remove all this `result` replacements and force people to use `complete` and `fail` explicitly. And i really like such change, but i really dislike proposal to...

@arnetheduck because `async` macro is untyped we can't get type information, and becasue we do not have type information its very hard to show meaningful error. And we are not...

@arnetheduck all the logic of result value happens here in `asyncmacro2.asyncSingleProc`. This part is responsible for verification of return value: https://github.com/status-im/nim-chronos/blob/master/chronos/asyncmacro2.nim#L164-L181 This part is responsible for creation of internal result...

Dualstack has been introduced in #456

I would expect that this issue was fixed, at least provided sample is now printing ``` Current counter is 0 ``` only on Linux with Nim 1.16.4 @KonradStaniec could you...

Could not agree with this change, because it breaks cross-platform behavior. FreeBSD for example keeps `so` symlinks for latest libraries without any `devel` packages. Also this statements are not totally...

@awr1 you are right, i always confuse this `implicit` / `explicit` terms.

Also you can read here https://nullprogram.com/blog/2018/05/27/. The most interesting parts of this article are [Procedure Linkage Tables](https://nullprogram.com/blog/2018/05/27/#procedure-linkage-tables) and [Indirect Dynamic Calls](https://nullprogram.com/blog/2018/05/27/#indirect-dynamic-calls).