commit | 6e4fca5882bdd6d00dfcc384473c1f612e00baa2 | [log] [tgz] |
---|---|---|
author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | Mon Jun 08 11:29:35 2020 +0000 |
committer | GitHub <noreply@github.com> | Mon Jun 08 11:29:35 2020 +0000 |
tree | 07fd36fde432cc8d42d23408a67133422a94fedb | |
parent | a5f427ced3ee0ec27041f0b7632b4baae6a736b2 [diff] | |
parent | b7db9f058ad51b7ba47db02b581a76b6756d74e8 [diff] |
Merge #4773 4773: Run|Debug hover actions. r=matklad a=vsrs ![hover_actions_run](https://user-images.githubusercontent.com/62505555/83335644-dfc1f780-a2b6-11ea-820b-ccaa82290e7d.gif) This hover actions work exactly like corresponding lenses. Co-authored-by: vsrs <vit@conrlab.com>
rust-analyzer is an experimental 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. If you want to get involved, check the rls-2.0 working group:
https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0
Work on rust-analyzer is sponsored by
https://rust-analyzer.github.io/manual.html#installation
If you want to contribute to rust-analyzer or 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.
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 rls-2.0 working group on Zulip:
https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frls-2.2E0
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.