docs.rs failed to build lingshu-lsp-0.10.0
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
lingshu-lsp
Why this crate? A coding agent that can only read files is flying blind. LSP integration
unlocks go-to-definition, find-references, diagnostics, and hover documentation — the same
signals your IDE uses to understand code.lingshu-lspis the async LSP client that lets
Lingshu query language servers at runtime, giving the agent IDE-grade code intelligence
without opening an editor.
Part of Lingshu — the Rust SuperAgent.
What's inside
| Component | Purpose |
|---|---|
LspClient |
Async LSP client (stdio transport, async-lsp) |
LspSession |
Manages textDocument/didOpen lifecycle per file |
LspQuery |
High-level helpers: goto_definition, find_references, hover, diagnostics |
LanguageId |
Maps file extensions to LSP language identifiers |
Add to your crate
[]
= { = "../lingshu-lsp" }
Usage
use ;
// Start rust-analyzer for the current workspace
let client = start.await?;
// Ask for the definition of a symbol at a specific location
let defs = goto_definition.await?;
for def in defs
// Pull diagnostics (warnings, errors) for a file
let diags = diagnostics.await?;
for d in diags
// Graceful shutdown
client.shutdown.await?;
Supported servers
Any LSP-compliant server works. Tested with:
| Language | Server |
|---|---|
| Rust | rust-analyzer |
| TypeScript / JS | typescript-language-server |
| Python | pyright, pylsp |
| Go | gopls |
The server binary must be on $PATH (or pass an absolute path to LspClient::start).
Full docs, guides, and release notes → lingshu.com