Jacek Sieka
Jacek Sieka
just-in-time execution using orc jit might be rebased occasionally, this is an experimentation ground
2eb46ca2212d5d6b9c8f5c78b282a2ec9bd1260b ``` nimbus --goerli --log-level=DEBUG ... DBG 2021-04-08 15:39:59.194+02:00 Handshake message not delivered topics="rlpx" tid=811532 file=rlpx.nim:131 peer=Node[206.189.192.240:30311] DBG 2021-04-08 15:39:59.194+02:00 Handshake message not delivered topics="rlpx" tid=811532 file=rlpx.nim:131 peer=Node[147.135.70.51:30304] DBG 2021-04-08...
This PR uses the facilities provided in https://github.com/status-im/nim-stew/pull/134 to support `?` in `async` proc's.
Async stack traces should not reside in the `msg` field of the exception - this field is meant for a short, human-readable description of the error that can be logged...
https://github.com/status-im/nim-chronos/blob/357baa52a0ea3da699c8229d97230c7f4340da92/chronos/transports/stream.nim#L1612 the above technique creates an unexpected reference to a variable that's passed in by value - this goes against the value semantics normally expected in nim - to make...
`getDispatcher` does lazy initialization - this means it's not possible to use the `chronos` API safely without introducing error handling in every call because it may raise an OSError (and...
Currently, an async proc looks like so: ```nim # Return int proc a(): Future[int] {.async.} # Return void proc b(): Future[void] {.async.} # Return void, take 2 proc c()] {.async.}...
A first step towards better threading support would be to remove the global dispatcher - that will allow a more library-like use with fewer mutable globals and better control over...
the chronos async loop should be a fairly simple matter: it's a loop that runs callbacks - yet when compiling a simple app like nim-beacon-chain there is 1.4MB of code...