Forgot to clarify (and can't edit comment anymore because apparently two hours is "post is too old"), but high-level overview of the compiler, data flow between subsections, logic behind certain edits and conditionals usually remains a mystery, and that's what makes understanding of the compiler so much harder. If you go into git blame history you might stumble upon commits like <https://github.com/nim-lang/Nim/commit/d933fde40d1232004c9eaa260dc6bd3dc376c272> that casually introduce **dependency between backend and semantic checking** (no big deal, really), and you are left scratching your head what exactly happened "on Feb 7, 2015"
And that is insanely taxing on the compiler development. You just can't know what the hell is happened there, can't ask, there is no proper support structure you can resort to for questions. And then you get to read comments like this <https://github.com/nim-lang/Nim/pull/19211#issuecomment-985981194> > I have no intention to follow this guideline so I cannot accept it. The > problem is real, but the solution is to write some simple tool that makes > "git log" more useful. followed by > pointed out that it would simplify his backporting efforts too, so I'll try > to follow this new guideline. [please](https://github.com/nim-lang/Nim/commit/0d6795a771e46b07244f3a3f43502602acbebdc3) [note](https://github.com/nim-lang/Nim/commit/ac37eed5a28042d50e23d9ae145f2d46b8dc5058) [the](https://github.com/nim-lang/Nim/commit/9888a29c3de09c73202b2a955e09e2a7b5e56ea4) "try" [word](https://github.com/nim-lang/Nim/commit/7d32425a577053bda356ca71c81d6701d8ad6372) (and some [more](https://github.com/nim-lang/Nim/commit/731eabc9309997775c8be41f3e5eb5512460aad0) [links](https://github.com/nim-lang/Nim/commit/2beefb9aa02171abce0512429336d86830025f3d))
