Adrià Arrufat 728f61a80d log: check the message rules at comptime ...

logToErased asserts that a log message is at most 30 characters of
plain text, but only in a debug build and only once the line actually
runs. A message on a rare path therefore ships fine and then panics on
whoever first reaches it: `serve --host 0.0.0.0` without
--advertise-host crashed on startup in every debug build, because
"advertising loopback for wildcard bind" is 38 characters.

Every message is a literal, so make the six wrappers take a comptime
msg and apply the same two rules through @compileError. The runtime
check stays as the backstop for the paths the compiler does not
analyse for the current target, and now reads the same constant.

Eleven messages were over the limit; shorten them. The detail already
lives in the kv pairs in each case. renderFailed takes its message as
comptime now, the only call site that passed a runtime one.

Note the check only covers code analysed for the target being built:
the two in Certificates.zig sit in an OS switch prong that Linux never
compiles, and were found by scanning the source rather than by the
compiler.

2026-09-23 11:20:42 +08:00

..

bidi

webdriver: execute

2026-09-22 16:31:52 +08:00

cdp

log: check the message rules at comptime

2026-09-23 11:20:42 +08:00

Driver.zig

WebDriver: add navigate

2026-09-16 14:05:49 +08:00

http.zig

log: check the message rules at comptime

2026-09-23 11:20:42 +08:00

Link.zig

make acquireArena names more consistent with each other

2026-09-14 07:44:21 +08:00

Server.zig

webdriver: execute

2026-09-22 16:31:52 +08:00

WS.zig

chore: make declarations private if they don't need to be public

2026-09-10 14:42:09 +08:00