ghostty.git/src/benchmark/TerminalParser.zig, branch main Unnamed repository; edit this file 'description' to name the repository. Zig 0.15: zig build test 2025-10-03T14:10:43+00:00 Mitchell Hashimoto m@mitchellh.com 2025-10-01T20:10:40+00:00 cb295b84a0ec274a43da59041fa4a199e799798d 






forgot to align buf
2025-09-18T18:20:41+00:00

Jacob Sandlund
jacob@jacobsandlund.com

2025-09-18T18:20:41+00:00

18e9989f63da95a730a0bf2bab9b5ae39dc9c71b












terminal: change OSC parser to explicit init to set undefined
2025-08-20T19:38:29+00:00

Mitchell Hashimoto
m@mitchellh.com

2025-08-20T19:06:09+00:00

131f170f8985cc89c960a02b1b3aae8f3ad9e7a5

This works around: https://github.com/ziglang/zig/issues/19148
This lets our `test-valgrind` command catch some issues. We'll have to
follow this pattern in more places but I want to do it incrementally so
things keep passing.

I **do not** want to blindly follow this pattern everywhere. I want to
start by focusing in only on the structs that set `undefined` as default
fields that we're also about to test in isolation with Valgrind. Its
just too much noise otherwise and not a general style I'm sure of; it's
worth it for Valgrind though.





This works around: https://github.com/ziglang/zig/issues/19148
This lets our `test-valgrind` command catch some issues. We'll have to
follow this pattern in more places but I want to do it incrementally so
things keep passing.

I **do not** want to blindly follow this pattern everywhere. I want to
start by focusing in only on the structs that set `undefined` as default
fields that we're also about to test in isolation with Valgrind. Its
just too much noise otherwise and not a general style I'm sure of; it's
worth it for Valgrind though.







benchmark: add GraphemeBreak and TerminalParser benchmarks
2025-07-09T22:06:24+00:00

Mitchell Hashimoto
m@mitchellh.com

2025-07-09T21:31:47+00:00

99ed984af2a12340a7b5b17326bc037044524ba4