Jacek Sieka
Jacek Sieka
### Summary The current implementation of closure iterators sees the implementation use a [duff's device](https://en.wikipedia.org/wiki/Duff%27s_device) to implement the state machine between each `yield`. A more efficient approach would be to...
### Summary Extend `void` handling to also allow `array[..., void]`. ### Description In https://github.com/nim-lang/Nim/issues/23419#issuecomment-2037606887, it is noted that an array of `void` is not allowed - this unnecessarily burdens generic...
### Description A variation on https://github.com/nim-lang/Nim/issues/23419, where the workaround of adding an empty field cannot be used. As a bonus on top, this shows how it breaks with a `static...
### Description ```nim import std/[sequtils, macros] type Future[T] = object InternalRaisesFuture[T, E] = object macro Raising*[T](F: typedesc[Future[T]], E: varargs[typedesc]): untyped = ## Given a Future type instance, return a type...
### Description ```nim import sequtils type F[T, E] = object proc start(v: int): F[void, (ValueError,)] = discard proc stop(v: int): F[void, tuple[]] = discard var a = mapIt([1, 2, 3],...
This PR is more or less a rewrite of the TCP transport to fix several race conditions and leaks that can happen during startup / shutdown as well as spurious...
To measure wall clock time, `perf -e task-clock` can be used: ``` perf record --call-graph dwarf,16000 -e task-clock ./testProf ``` ``` 99.92% 0.19% testProf testProf [.] main | --99.73%--main readRandFileValue...
Google runs infrastructure that automatically fuzzes libraries, and snappy has fuzzing set up - investigate whether snappy can be added as a project assuming they can treat nim like C....
This PR fails weirdly on some platforms - the fix appears to be to remove the call to `ensureRunway` as is done in https://github.com/status-im/nim-snappy/pull/10/commits/9d1d2323d98fb78e92b925bdc2bf1cb145df6943