dfac970cc7e06ef427446073978e8fa004b535e4
Positions were being calculated by looking at the *first* character, which would cause the same character to be visited twice. Now, if the character is a null byte (\0), it won't advance the position at all. The null byte should be a safe sentinel value to use because it (hypothetically) shouldn't be showing up in a source file. This will probably cause a hang if a file that starts with null bytes, but that's a problem for future me. Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
Description
Bad stack-based language
Languages
Rust
100%