Jacek Sieka
Jacek Sieka
As of https://github.com/nim-lang/nimble/pull/1131, `nimble` can build nim - however, as part of building nim-the-compiler, it also builds a toolchain including `nimble` - this can lead to the user instance of...
``` /nimble/src/nimblepkg/sha1hashes.nim(6, 42) Error: cannot open file: ../../dist/checksums/src/checksums/sha1 ``` 412af022a44157dd17118432fba825da9f204125
Reentrancy causes event reordering and stack explosions, in addition to leading to hard-to-debug scenarios. Since none of chronos is actually tested under reentrant conditions (ie that all features such as...
Strict future access is now always enabled, making it a panic to access value/error when the Future is still pending - `read` and `readError` raise catchable exceptions instead which may...
Although https://github.com/status-im/nim-chronos/pull/418 was ultimately not merged, it contains an idea to improve performance in general: instead of allocating a separate `var result` that gets injected, it instead injects a `template...
Per the floodsub spec, a message has only one (mandatory) topic: https://github.com/libp2p/specs/blob/master/pubsub/README.md#the-message Our code however uses a [`seq`](https://github.com/status-im/nim-libp2p/blob/28609597d104a9be880ed5e1648e1ce18ca9dc38/libp2p/protocols/pubsub/rpc/messages.nim#L44) for topics, likely due to implementing an ancient version of the protocol...
Consider: * peer A sends a message to us which is sent to validation - peer B sends the same message to us and when the message validates, we skip...