X-Git-Url: https://git.lizzy.rs/?a=blobdiff_plain;f=README.md;h=5dcb8e12491aa64741090fccae4cca532da256c9;hb=4103068ad22216d2479dcb0534a1104dac933965;hp=9504e433d12a26272900266ae49e3c282a80a357;hpb=b5cb53ea93f2573b76515a0b651eeb13bb5a74f0;p=rust.git diff --git a/README.md b/README.md index 9504e433d12..5dcb8e12491 100644 --- a/README.md +++ b/README.md @@ -42,14 +42,13 @@ powered editor. ## Current Status and Plans Rust analyzer aims to fill the same niche as the official [Rust -Language Server](https://github.com/rust-lang-nursery/rls), but -better. It was created because @matklad is not satisfied with RLS -original starting point and current direction. More details can be -found [in this -thread](https://internals.rust-lang.org/t/2019-strategy-for-rustc-and-the-rls/8361). -The core issue is that RLS works in the "wait until user stops typing, -run the build process, save the results of the analysis" mode, which -arguably is the wrong foundation for IDE (see the thread for details). +Language Server](https://github.com/rust-lang-nursery/rls), but uses a +significantly different architecture. More details can be found [in +this +thread](https://internals.rust-lang.org/t/2019-strategy-for-rustc-and-the-rls/8361), +but the core issue is that RLS works in the "wait until user stops +typing, run the build process, save the results of the analysis" mode, +which arguably is the wrong foundation for IDE. Rust Analyzer is a hobby project at the moment, there's exactly zero guarantees that it becomes production-ready one day. @@ -92,7 +91,7 @@ notes. - `algo`: generic tree algorithms, including `walk` for O(1) stack space tree traversal (this is cool) and `visit` for type-driven visiting the nodes (this is double plus cool, if you understand how - `Visitor` works, you understand libsyntax2). + `Visitor` works, you understand rust-analyzer). ### `crates/ra_editor` @@ -132,7 +131,7 @@ A CLI interface to libsyntax ### `crate/tools` -Code-gen tasks, used to develop libsyntax2: +Code-gen tasks, used to develop rust-analyzer: - `cargo gen-kinds` -- generate `ast` and `syntax_kinds` - `cargo gen-tests` -- collect inline tests from grammar