From 898c61ee7cddaade523885bb9b02a89678b00fcc Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Sun, 27 Sep 2026 22:41:19 -0300 Subject: Give the message log to Messages as its own fields Not a pure move: state moves. Pardes's three message-log fields (`messages: [message_log]LoggedMessage`, `messages_head`, `messages_len`) become the fields of Messages.zig itself (`log`, `head`, `len`), and Pardes embeds one as `messages: Messages = .{}`. messageLog reads only the ring, so it now takes `m: *const Messages` and is called `p.messages.messageLog(i)` (Output's +Messages view and the log test); logMessage still needs the panes and the 9P event log, so it keeps `p: *Pardes` and writes `p.messages.log/head/len`. No behaviour change. Co-Authored-By: Claude Opus 5.5 --- src/pardes.zig | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) (limited to 'src/pardes.zig') diff --git a/src/pardes.zig b/src/pardes.zig index 44f0d2ea..d2ac5868 100644 --- a/src/pardes.zig +++ b/src/pardes.zig @@ -3777,12 +3777,8 @@ pub const Pardes = struct { /// The in-program answers behind every unimplemented host method. Per /// instance, so several cores behind one fan-out host stay independent. fallback: host_io.Fallback, - /// The message-row log: a fixed ring, never allocated, never grown. See - /// `logMessage` and the `Messages` builtin. - messages: [limits.message_log]Messages.LoggedMessage = @splat(.{}), - /// Next slot to write. `messages_len` saturates at the ring's size. - messages_head: usize = 0, - messages_len: usize = 0, + /// The message-row log (see Messages.zig). + messages: Messages = .{}, in_q: [64]Event = undefined, in_head: usize = 0, in_len: usize = 0, -- cgit v1.3