haxscramper

For the sake of seeing this discussion moving forward, let's assume that some library was picked to be the baseline for implementing the std module -- what would be the...

> The Nim CI should have a measure to calculate the comment ratio of the code. Current breakdown of the compiler **documentation** (single-hash comments are not considered documentation) comment ratio...

Another obvious statistics while we are at it - this heatmap shows correlation of edits between different parts of the project code. The left side shows total number of edits...

I'm writing a tool for this kind of analysis https://github.com/haxscramper/code_forensics - for now it is a proof of concept, but I'm working on more stats such as an average commit...

[sigmatch.paramTypesMatch](https://github.com/nim-lang/Nim/blob/cde6b2aab8f67291eca5375a067f97e98b7593ee/compiler/sigmatch.nim#L2209) has a total of __**>>NINE

For the reference - it was a joke, although maybe someone can interpret it as an example starting point or example of how code should **not** be written. I was...

The idea is relatively sound, but the number of conflicts and the pace of cleanup for the nodes suggest I should close this PR for the time being -- in...

I think I can work on this later on, after https://github.com/nim-works/nimskull/pull/476 and https://github.com/nim-works/nimskull/pull/135 are merged and general test cleanup is complete.

Closing this PR for the time being -- conflicts started to pile up and IMO this can be re-opened when needed, right now it is just a bit confusing to...

Additionally, expanding tilde makes it harder to copy-paste things from the history to documentation, for sending code to the others as example. This is more of a niche case and...