nim-chronos icon indicating copy to clipboard operation
nim-chronos copied to clipboard

Chronos - An efficient library for asynchronous programming

Results 84 nim-chronos issues
Sort by recently updated
recently updated
newest added

Your goal will be to create a benchmark testing asyncdispatch2 against the Nim's existing asyncdispatch module and the best competing frameworks available in other programming languages. A suitable choice would...

bounty
bounty-xl
bounty-awaiting-approval
awaiting-bounty-criteria

```nim proc works(): Future[int] {.async.} = return 53 proc works2(): Future[int] {.async.} = result = 53 proc broken(): Future[int] {.async.} = 53 # Error: expression '53' is of type 'int...

```nim DatagramCallback* = proc(transp: DatagramTransport, remote: TransportAddress): Future[void] {.gcsafe.} message: seq[byte], remote: TransportAddress, error: OSErrorCode): Future[void] ``` message - UDP message bytes. If len(message) == 0 you need to check...

Since Jacek is reviewing the AD2 APIs and suggesting changes, here is one small change I want to suggest. The timer APIs are currently accepting a closure taking an opaque...

- [x] finishing bench bot implementation - [x] add participant: rust actix - [x] add participant: go-lang fasthttp - [x] add participant: c libreactor - [x] polishing benchmark report -...

@nitely has worked on a benchmark for asyncdispatch2, aiming to compare it to the older asyncdispatch and also to some well-known fast frameworks in other languages. I'm creating this pull...

Generate documentation on each push to master: https://status-im.github.io/nim-chronos/docs/chronos.html And some touch ups on existing documentation