ringabout

Whether https://github.com/nim-lang/Nim/issues/21422 is fixed is not clear to me.

https://forum.nim-lang.org/t/7969#50770 seems to be broken: "Couldn't render historic post in #50770"  And it cannot be rendered properly in the search results.

Doc comments still need to explain every quirk in the procs because the Nim compiler is too complex. There are some procs has hundreds or even thousands of lines. It...

> if we have a mechanism to deal with such an idea of a "community sponsored bounty" or if we best handle this all individually. There is. See the bounty...

I'm going to push the setup to set an example for later updates when this plan is accepted.

I agree that commenting is not appropriate. It is better to have a clear code structure. The point that "Rewrite bad code; don't write comments" from https://www.youtube.com/watch?v=NLebZ3XT92E&t=308s seems fair. The...

> Rewrite the codegen to be based on a stream of tokens, not based on Ropes. (Memory consumption, performance.) I might work on it in a few days, since it...

See also https://github.com/nim-lang/Nim/pull/20609

update: https://github.com/nim-lang/Nim/issues/19464 is fixed