This appears to actually not be a new bug, but an old one. The difference is that the compiler currently has overflow and range checks enabled.
The underlying problem is that line and column information for error reporting in the lexer is represented as 16-bit integers in order to save space (as that information is used internally in every lexer token). This could run into overflow issues before, they just were ignored. A temp fix would be to make the relevant fields in `TLineInfo` in `compiler/lineinfos.nim` 32-bit integers, but that would up memory consumption unnecessarily for most projects. An alternative solution would be to use saturation arithmetic on line and column numbers, i.e. the values would cap at `uint16.high` or `int16.high` and to add information to error messages to note that column/line information is off.
