commit | 5bf2f85c8054d80424899fa581db1b192230efb5 | [log] [tgz] |
---|---|---|
author | bors <bors@rust-lang.org> | Thu May 09 11:59:04 2024 +0000 |
committer | bors <bors@rust-lang.org> | Thu May 09 11:59:04 2024 +0000 |
tree | 5306e894816c93cb6c43fd3bf0f8f95123cba6e7 | |
parent | 7d1b3a6607beea14fe091008a9080ffa3ff578ab [diff] | |
parent | d993f9d1c9e686a3bdcb1de5440122ebc3393132 [diff] |
Auto merge of #17208 - Wilfred:log_error_from_threads, r=Veykril fix: Report both IO errors and main_loop errors If rust-analyzer receives a malformed LSP request, the IO thread terminates with a meaningful error, but then closes the channel. Once the channel has closed, the main_loop also terminates, but it only has RecvError and can't show a meaningful error. As a result, rust-analyzer would incorrectly claim that the client forgot to shutdown. ``` $ buggy_lsp_client | rust-analyzer Error: client exited without proper shutdown sequence ``` Instead, include both error messages when the server shuts down.
rust-analyzer is a modular compiler frontend for the Rust language. It is a part of a larger rls-2.0 effort to create excellent IDE support for Rust.
https://rust-analyzer.github.io/manual.html#installation
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, check the ./docs/dev folder.
If you want to use rust-analyzer's language server with your editor of choice, check the manual folder. It also contains some tips & tricks to help you be more productive when using rust-analyzer.
See the corresponding 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.