nim-chronos
nim-chronos copied to clipboard
status-im
Chronos - An efficient library for asynchronous programming
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.}...
Async stream ones are public, these are private/internal still. https://github.com/status-im/nim-chronos/blob/d8f8e3d9fc3b933904037750e5ad1799257356b7/chronos/transports/stream.nim#L67-L69
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...
the unit test suite is not written in an exception safe way - this is problematic because: * tests are often a good source of example code - if they...
Details https://github.com/nim-lang/Nim/issues/12530
At this point the changes are out for testing/breaking purposes. Please report any issues you find.
