You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: crates/proc-macro-srv-cli/README.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,12 +9,12 @@ rust-analyzer uses a RPC (via stdio) client-server architecture for procedural m
9
9
1. Proc macros are dynamic libraries that can segfault, bringing down the entire process, so running them out of process allows rust-analyzer to recover from fatal errors.
10
10
2. Proc macro dylibs are compiled against a specific rustc version and require matching internal APIs to load and execute, as such having this binary shipped as a rustup component allows us to always match the rustc version irrespective of the rust-analyzer version used.
11
11
12
-
## The `sysroot-abi` Feature
12
+
## The `in-rust-tree` Feature
13
13
14
-
**The `sysroot-abi` feature is required for the binary to actually function.** Without it, the binary will return an error:
14
+
**The `in-rust-tree` feature is required for the binary to actually function.** Without it, the binary will return an error:
15
15
16
16
```
17
-
proc-macro-srv-cli needs to be compiled with the `sysroot-abi` feature to function
17
+
proc-macro-srv-cli needs to be compiled with the `in-rust-tree` feature to function
18
18
```
19
19
20
20
This feature is necessary because the proc-macro server needs access to unstable rustc internals (`proc_macro_internals`, `proc_macro_diagnostic`, `proc_macro_span`) which are only available on nightly or with `RUSTC_BOOTSTRAP=1`.
@@ -24,10 +24,10 @@ rust-analyzer is a stable toolchain project though, so the feature flag is used
0 commit comments