LSP

Editor integration via the Sounio Language Server (sounio-lsp).

LSP

LSP support exists in the repo, but it is the clearest example of why docs must distinguish “implemented somewhere in the tree” from “enabled in the checked public artifact.” This page documents both sides of that distinction.

Current contract

  • The checked public JIT artifact reports LSP as disabled.
  • The repo still contains a dedicated LSP implementation surface under self-hosted/lsp/ and editor integration material under editors/vscode/.
  • Public docs should describe LSP as a feature-gated or alternate-build capability, not as something guaranteed by the default checked binary.

Where it lives

  • self-hosted/lsp/protocol.sio maps the protocol layer.
  • self-hosted/lsp/diagnostics.sio, hover.sio, goto_def.sio, completions.sio, rename.sio, and code_actions.sio show the active feature surface.
  • editors/vscode/ is the obvious place to inspect editor packaging and configuration.

Artifact check and implementation path

export SOUC_BIN="$(pwd)/artifacts/omega/souc-bin/souc-linux-x86_64-jit"
"$SOUC_BIN" info

The repo also contains LSP integration entry points under:

  • self-hosted/lsp/
  • tools/lsp/sounio-lsp.sh
  • editors/vscode/

Those are implementation surfaces, not proof that the checked public artifact ships LSP enabled by default. This repo snapshot also does not expose a single root-level Cargo workflow that produces an LSP-enabled main compiler binary.

Documentation guidance

  • Lead with the checked artifact status.
  • Then describe the repo implementation path for contributors and advanced users.
  • Avoid saying “Sounio ships an LSP by default” unless you are documenting a specific artifact that actually enables it.