From c3d0b84b7961ae26d2d654e7120821cc2d83d20d Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Mon, 24 Aug 2026 10:56:05 -0300 Subject: host: the core owns the event loop; every platform becomes a vtable of optional methods --- docs/lsp.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/lsp.md') diff --git a/docs/lsp.md b/docs/lsp.md index 0125f958..54ffd764 100644 --- a/docs/lsp.md +++ b/docs/lsp.md @@ -33,9 +33,9 @@ about thirty lines per shell: `tty.zig` uses `io.concurrent` + the vaxis loop queue, `gui.zig` uses a detached thread + the mutex queue it already had. The web shell compiles in no backend at all (`zls_backend` is off for wasm), which makes `lsp.supports` empty, which makes `lspRequest` return before it emits — -so on the web the effect is never even raised. `web.zig` carries a prong for it -and exports `pardes_lsp_response` anyway; both are unreachable in the shipped -configuration and wait for a host that links a backend. +so on the web the effect is never even raised. `web.zig` leaves the host's +`lsp` method null and exports nothing for a response; a host that links a +backend would add both. Three rules make it safe: -- cgit v1.3