diff options
| author | Ian Johnson <ian@ianjohnson.dev> | 2024-09-09 22:23:45 -0400 |
|---|---|---|
| committer | Veikka Tuominen <git@vexu.eu> | 2024-09-10 13:34:33 +0300 |
| commit | 90075345519f165a0164c52b62b78453068c6ce6 (patch) | |
| tree | ca83ba36ab298b92db9be64cb46a42a1a608166b /src/Compilation.zig | |
| parent | d6d09f4ea7cc590035bf8af6617f93767423c691 (diff) | |
| download | zig-90075345519f165a0164c52b62b78453068c6ce6.tar.gz zig-90075345519f165a0164c52b62b78453068c6ce6.zip | |
std.zig.tokenizer: simplify line-based tokens
Closes #21358
Closes #21360
This commit modifies the `multiline_string_literal_line`, `doc_comment`,
and `container_doc_comment` tokens to no longer include the line ending
as part of the token. This makes it easier to handle line endings (which
may be LF, CRLF, or in edge cases possibly nonexistent) consistently.
In the two issues linked above, Autodoc was already assuming this for
doc comments, and yielding incorrect results when handling files with
CRLF line endings (both in Markdown parsing and source rendering).
Applying the same simplification for multiline string literals also
brings `zig fmt` into conformance with
https://github.com/ziglang/zig-spec/issues/38 regarding formatting of
multiline strings with CRLF line endings: the spec says that `zig fmt`
should remove the CR from such line endings, but this was not previously
the case.
Diffstat (limited to 'src/Compilation.zig')
0 files changed, 0 insertions, 0 deletions
