/ Whether the crate is a proc-macro crate. / The set of cfgs activated for a given crate, like / source can't refer to files in another source. / rust-analyzer assumes that files from one / If two crates share an `.rs` file in common, / Different crates can share the same `source`. / recursively, unless a subdirectory is in / files under `root_module.parent` can belong / By default, rust-analyzer assumes that only / Optionally specify the (super)set of `.rs`
/ assumes that non-member crates don't change). / performance optimizations (rust-analyzer / library and 3rd party crates to enable / Set this to `false` for things like standard / (members are the crates which reside inside / By default, inferred from the `root_module` / Should this crate be treated as a member of / Path to the root module of the crate. / key for semantically-significant crate names. / Optional crate name used for display purposes, / dependencies as well as sysroot crate (libstd, / The set of crates comprising the current / several different "sysroots" in one graph of / dependencies yourself and, for example, have / if you omit this path, you can specify sysroot / If provided, rust-analyzer automatically adds / It should point to the directory where std,
/ Path to the directory with *source code* of
0 kommentar(er)
