Timothee Cour

I'd be ok with `$nim/lib/extras/` or `$nim/extras/` as it shouldn't be restricted to doc stuff there are 2 option: option 1: extras=`$nim/lib/extras/` option 2: extras=`$nim/extras/` with either option we can...

> This makes it less appealing to ship the .css file in the lib/ dir. I would expect nim doc .. command to Just Work whether or not the user...

> how can I fix this? PR welcome to proceed as described here: https://github.com/nim-lang/Nim/issues/14424#issuecomment-849803994

> $nim is /usr if the nim binary is /usr/bin/nim and it's the root directory (!) if the binary is in /bin/nim it's not appropriate to add folders or files...

> I think the needs this mechanism is addressing should be discussed in an RFC first. => filed https://github.com/nim-lang/RFCs/issues/400 > The compiler command line is already quite complicated, and I...

it's intended as a replacement for mapLiterals which is already in sequtils; the 4 examples showing limitations of `mapLiterals` are IMO a strong enough reason; require a 3rd party library...

> Is there a reason mapLiterals can't be expanded to incorporate this functionality? that would be a breaking change, and would not reflect the semantics of mapItLit, which doesn't care...

how about `mapItContainer` ?

I've now removed the `{.deprecated.}` mention. > but it sucked for 4 years already and nobody cared. there are 2 types of APIs: the ones people complain about and the...

* https://github.com/nim-lang/RFCs/issues/228 would allow nicer syntax 123'bigint instead of initBigInt"123" but can be done as a syntax upgrade so is not a blocker. * https://github.com/FedeOmoto/bignum didn't get an update in...