@@ -57,6 +57,12 @@ build procedural macros. The command is required to output json
5757and should therefore include `--message-format=json` or a similar
5858option.
5959
60+ If there are multiple linked projects/workspaces, this command is invoked for
61+ each of them, with the working directory being the workspace root
62+ (i.e., the folder containing the `Cargo.toml` ). This can be overwritten
63+ by changing `#rust-analyzer.cargo.buildScripts.invocationStrategy#` and
64+ `#rust-analyzer.cargo.buildScripts.invocationLocation#` .
65+
6066By default, a cargo invocation will be constructed for the configured
6167targets and features, with the following base command line:
6268
@@ -206,9 +212,11 @@ If you're changing this because you're using some tool wrapping
206212Cargo, you might also want to change
207213`#rust-analyzer.cargo.buildScripts.overrideCommand#` .
208214
209- If there are multiple linked projects, this command is invoked for
210- each of them, with the working directory being the project root
211- (i.e., the folder containing the `Cargo.toml` ).
215+ If there are multiple linked projects/workspaces, this command is invoked for
216+ each of them, with the working directory being the workspace root
217+ (i.e., the folder containing the `Cargo.toml` ). This can be overwritten
218+ by changing `#rust-analyzer.cargo.check.invocationStrategy#` and
219+ `#rust-analyzer.cargo.check.invocationLocation#` .
212220
213221An example command would be:
214222
@@ -244,6 +252,11 @@ with `self` prefixed to them when inside a method.
244252--
245253Whether to add parenthesis and argument snippets when completing function.
246254--
255+ [[rust-analyzer.completion.fullFunctionSignatures.enable]]rust-analyzer.completion.fullFunctionSignatures.enable (default: `false` )::
256+ +
257+ --
258+ Whether to show full function/method signatures in completion docs.
259+ --
247260[[rust-analyzer.completion.limit]]rust-analyzer.completion.limit (default: `null` )::
248261+
249262--
0 commit comments