fix!: make lsp-server `Response` type closer aligned to JSON-RPC From [the JSON-RPC 2.0 protocol](https://www.jsonrpc.org/specification#response_object): > result > This member is REQUIRED on success. > This member MUST NOT exist if there was an error invoking the method. > The value of this member is determined by the method invoked on the Server. > error > This member is REQUIRED on error. > This member MUST NOT exist if there was no error triggered during invocation. > The value for this member MUST be an Object as defined in section 5.1. > > ... > > Either the result member or error member MUST be included, but both members MUST NOT be included. The current typing of the `Response` object allows both the `result` and `error` members to be present, or for neither to be present. This commit strengthens the typing of the response to prevent these cases from being expressed. This is a breaking change. The response kind definition is borrowed from the [tower-lsp](https://github.com/ebkalderon/tower-lsp) definition.
rust-analyzer is a language server that provides IDE functionality for writing Rust programs. You can use it with any editor that supports the Language Server Protocol (VS Code, Vim, Emacs, Zed, etc).
rust-analyzer features include go-to-definition, find-all-references, refactorings and code completion. rust-analyzer also supports integrated formatting (with rustfmt) and integrated diagnostics (with rustc and clippy).
Internally, rust-analyzer is structured as a set of libraries for analyzing Rust code. See Architecture in the manual.
https://rust-analyzer.github.io/book/installation.html
If you want to contribute to rust-analyzer check out the CONTRIBUTING.md or if you are just curious about how things work under the hood, see the Contributing section of the manual.
If you want to use rust-analyzer's language server with your editor of choice, check the manual. It also contains some tips & tricks to help you be more productive when using rust-analyzer.
See the security and privacy sections of the manual.
For usage and troubleshooting requests, please use “IDEs and Editors” category of the Rust forum:
https://users.rust-lang.org/c/ide/14
For questions about development and implementation, join rust-analyzer working group on Zulip:
https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frust-analyzer
rust-analyzer is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0).
See LICENSE-APACHE and LICENSE-MIT for details.