Timothee Cour

* not everything in this list is equally valuable, we should focus on most common first (subjective, yes). > `lrint | Y (round)` * we actually don't have `lrint` and...

> This can be worked around by putting import system except repr,$ at the top of your file but unfortunately that also drops a lot of other useful procedures. We...

> it's not required either. OP also mentioned `$`: > I also tried to overwrite $(type) but ultimately made by own toStr procedure for types. > putting import system except...

note: there is a (very) partial support for cyclic imports, see http://nim-lang.github.io/Nim/manual.html#modules > Recursive module dependencies are allowed, but slightly subtle (see corresponding example + limitations)

@Araq done => https://github.com/nim-lang/Nim/pull/14747

@Araq > We already have tyAlias, what's the difference between tyAlias and tyAliasSym? * I can only infer `tyAlias` from reading code since it's undocumented, nor was it documented or...

@Araq > unwritten RFC "nullary non-overloaded templates should be resolved early and allow for aliasing of the template body". Can we unify aliases and nullary templates? > Ok, let me...

> Plenty of Nim developers think that there is considerable overlap with template and/or const https://github.com/nim-lang/Nim/pull/11992 has the +1's amongst all PR's to date, and I haven't seen any explanation...

(this is not an argument against a generic bitable) There are too many table (or table-like) implementations in nim repo (see https://github.com/nim-lang/RFCs/issues/200#issuecomment-597333572 and https://github.com/nim-lang/Nim/pull/13418#issuecomment-588963291) in particular the ones that are...

because I much prefer your original proposal in https://github.com/nim-lang/RFCs/issues/19#issuecomment-173529871 this new RFC prompted me to go ahead and implement your original proposal, I have a PR in the works for...