1 Nov 2026
Elixir character literals no longer swallow comments
- What was broken
- Elixir writes a character's code as a question mark before it. A quote written that way opened a string, so comments up to the next quote counted as code.
- What I changed
- Those forms now count as plain code, since a question mark before a quote means nothing else in Elixir.
- Why it matters
- Elixir code that parses strings gets correct comment and code counts.
see the code, #818 ↗ (opens in a new tab)
1 Nov 2026
A quote character in OCaml and Nim no longer swallows comments
- What was broken
- In OCaml and Nim, a quote written as a single character opened a string that ran on to the next quote, so comments in between counted as code.
- What I changed
- That character form is now recognised and closes right away. Type variables and number suffixes that start with an apostrophe are left alone.
- Why it matters
- OCaml and Nim files report the correct split of code and comments.
see the code, #817 ↗ (opens in a new tab)
1 Nov 2026
PowerShell files count comments correctly around single quotes
- What was broken
- Single-quoted PowerShell strings were not understood, so a quote mark inside one started a fake string or comment. Real scripts came out with wrong code and comment counts.
- What I changed
- Single-quoted strings and here-strings are now read as strings, so what is inside them can't start anything else.
- Why it matters
- People measuring PowerShell projects get the real number of code and comment lines.
see the code, #816 ↗ (opens in a new tab)
← every project