diff options
| author | Andrew Kelley <andrew@ziglang.org> | 2021-02-22 23:25:12 -0700 |
|---|---|---|
| committer | Andrew Kelley <andrew@ziglang.org> | 2021-02-22 23:25:12 -0700 |
| commit | 1e3a200ba604c8d19fcc1119d01c2e80f2a8beca (patch) | |
| tree | b4044c94ee618ffb72f33cbafb83e4c482a4d509 /src/codegen | |
| parent | 1253903fef07d7fd0435310f474bfe2745b41405 (diff) | |
| download | zig-1e3a200ba604c8d19fcc1119d01c2e80f2a8beca.tar.gz zig-1e3a200ba604c8d19fcc1119d01c2e80f2a8beca.zip | |
zig fmt: array literal with hint
This regresses the test case of `zig fmt` deleting empty line comments.
Two open questions here:
* What should the rules be about deleting empty line comments?
It makes sense usually, but for array initization, empty line
comments cause a line break, affecting the row/column alignment.
Perhaps we should therefore respect all empty line comments?
Or should we special case array initializations?
* If we decide to special case some kinds of line comments to respect
them (which is status quo!), how should that be implemented?
Diffstat (limited to 'src/codegen')
0 files changed, 0 insertions, 0 deletions