From cb13e4a2ca6d2f4c19b6a9959288142dffc4c32c Mon Sep 17 00:00:00 2001 From: Toby Fleming Date: Sat, 31 Jul 2021 15:26:59 -0700 Subject: Rust project supports proc-macro dependent crates --- docs/user/manual.adoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/user/manual.adoc b/docs/user/manual.adoc index 000a95b1003..6f00da3178a 100644 --- a/docs/user/manual.adoc +++ b/docs/user/manual.adoc @@ -578,6 +578,8 @@ interface Crate { /// the `env!` macro env: : { [key: string]: string; }, + /// Whether the crate is a proc-macro crate. + is_proc_macro: bool; /// For proc-macro crates, path to compiled /// proc-macro (.so file). proc_macro_dylib_path?: string; @@ -597,7 +599,7 @@ Specifically, the `roots` setup will be different eventually. There are three ways to feed `rust-project.json` to rust-analyzer: -* Place `rust-project.json` file at the root of the project, and rust-anlayzer will discover it. +* Place `rust-project.json` file at the root of the project, and rust-analyzer will discover it. * Specify `"rust-analyzer.linkedProjects": [ "path/to/rust-project.json" ]` in the settings (and make sure that your LSP client sends settings as a part of initialize request). * Specify `"rust-analyzer.linkedProjects": [ { "roots": [...], "crates": [...] }]` inline. -- cgit 1.4.1-3-g733a5