acmefs: pardes --fs serves acme's control filesystem over raw Linux FUSE

1 files changed, 8 insertions, 0 deletions

diff --git a/src/host.zig b/src/host.zig
index d3e93d36..e44318da 100644
--- a/src/host.zig
+++ b/src/host.zig
@@ -107,6 +107,14 @@ pub const Host = struct {
         /// completed and the core would apply it to whatever holds that id now.
         pull_lsp: ?*const fn (ctx: ?*anyopaque, req: LspRequest) void = null,
         pull_pipe: ?*const fn (ctx: ?*anyopaque, id: u32) void = null,
+        /// Hand one filesystem answer back to whoever asked for it (a FUSE
+        /// `write(2)` to /dev/fuse). `bytes` is the payload the core resolved
+        /// for this reply and is borrowed for the length of this call — it may
+        /// point straight into a pane's text, so a host that needs it later
+        /// copies it. A push and not a pull: the answer is already computed,
+        /// and a second host serving the same mount is not a thing that
+        /// happens (the transport that asked is the one holding the request).
+        push_fs_reply: ?*const fn (ctx: ?*anyopaque, reply: *const pardes.acmefs.Reply, bytes: []const u8) void = null,
     };
 };