Jacek Sieka
Jacek Sieka
### Description ```nim type A = object field: int proc works(a: A): lent int = a.field proc x(a: A): lent int = case true of true: a.field of false: a.field...
When `nimble` builds `nim`, it does not use the available parallelism when building csources which significantly slows down the build.
port of #20781
`nimbus` should support the same logging options as eth2 by reusing the shared binary support, similar to https://github.com/status-im/nimbus-eth1/pull/2488 - in particular, this allows autodetecting things like tty color support etc
When passing `--data-dir`, we want to ensure that eth1 and eth2 can share the same data directory - this requires reviewing where the databases and various configuration files are located...
Similar to https://github.com/status-im/nimbus-eth2/issues/4839, nimbus should create dual-stack listeners by default for public listeners and use ipv6 if advertised by other peers - this extends to all kinds of sockets.
https://github.com/status-im/nim-eth/blob/master/eth/p2p/rlpx.nim#L25 By now, this must be beyond obsolete
Execution client logging options have not kept up with eth2 and do not support tty autodetection for colors - since the dependency now exists, use logging setup from `nimbus_binary_common` to...
### Description ```nim import std/macros macro evalOnceAs*(exp, alias: untyped): untyped = expectKind(alias, nnkIdent) let body = nnkStmtList.newTree() val = if exp.kind == nnkSym: # The symbol can be used directly...
### Description The following snippet results in a dangling pointer for the array access: ```nim type ArrayBuf = object buf: array[32, byte] n: int template data*(bParam: ArrayBuf): openArray = block:...