Eugene Kabanov
Eugene Kabanov
Its actually not received twice, `epoch` value is different.
Why we should keep references to other projects if this projects do not keep references to `chronos`? So as an example: 1. `nim-metrics` do not have first class reference like...
> > Why we should keep references to other projects > > these references provide examples for how to use chronos - since the project itself lacks docs / examples...
`asyncproc` requires some procedures which `chronos` do not have, tricks with `RegisterWaitForSingleObject`, https://github.com/nim-lang/Nim/blob/devel/lib/pure/asyncdispatch.nim#L1002-L1018
Also `AsyncPipe` is not needed actually we can use `StreamTransport` instances.
What the main goal of this PR? Right now i see it very subjective.
Manual `Future[T]` management is unsafe by design. All this `Future[T].addCallback()` and closure procedures do not make code simpler. Right now `chronos` allows both paradigms to be combined (`callback soup` and...
Sorry but i'm still not completely convinced that such primitives are needed. Tests refactoring could be merged.
`SEH` and `DWARF` has only meaning for x86 and if you check winlibs you will find that on x86 it has DWARF suffix, also i have not found any issues/crashes...
Also i want to put this information link here https://wiki.qt.io/MinGW-64-bit Which explains same things but from QT developers. From this one i even see that we should deprecated posix threads...