diff options
author | Laurențiu Nicola <[email protected]> | 2021-06-15 18:05:16 +0100 |
---|---|---|
committer | Laurențiu Nicola <[email protected]> | 2021-06-15 18:07:59 +0100 |
commit | cbf53ba2514a0a19ba8fc45348e0e6610cb88859 (patch) | |
tree | 6802a3a75e113a634e52a7bbc2650c6aaaa37b2b /docs | |
parent | 6cbb18e570b89401e6e63fd89a719b87ab362ece (diff) |
Consolidate the privacy notes
Diffstat (limited to 'docs')
-rw-r--r-- | docs/user/manual.adoc | 11 |
1 files changed, 8 insertions, 3 deletions
diff --git a/docs/user/manual.adoc b/docs/user/manual.adoc index 9a8d76700..d5f8dbb1d 100644 --- a/docs/user/manual.adoc +++ b/docs/user/manual.adoc | |||
@@ -609,9 +609,14 @@ Here is a **non-exhaustive** list of ways to make rust-analyzer execute arbitrar | |||
609 | * VS Code plugin reads configuration from project directory, and that can be used to override paths to various executables, like `rustfmt` or `rust-analyzer` itself. | 609 | * VS Code plugin reads configuration from project directory, and that can be used to override paths to various executables, like `rustfmt` or `rust-analyzer` itself. |
610 | * rust-analyzer's syntax trees library uses a lot of `unsafe` and hasn't been properly audited for memory safety. | 610 | * rust-analyzer's syntax trees library uses a lot of `unsafe` and hasn't been properly audited for memory safety. |
611 | 611 | ||
612 | rust-analyzer itself doesn't access the network. | 612 | == Privacy |
613 | The VS Code plugin doesn't access the network unless the nightly channel is selected in the settings. | 613 | |
614 | In that case, the plugin uses the GitHub API to check for and download updates. | 614 | The LSP server performs no network access in itself, but runs `cargo metadata` which will update or download the crate registry and the source code of the project dependencies. |
615 | If enabled (the default), build scripts and procedural macros can do anything. | ||
616 | |||
617 | The Code extension automatically connects to GitHub to download updated LSP binaries and, if the nightly channel is selected, to perform update checks using the GitHub API. For `rust-analyzer` developers, using `cargo xtask release` uses the same API to put together the release notes. | ||
618 | |||
619 | Any other editor plugins are not under the control of the `rust-analyzer` developers. For any privacy concerns, you should check with their respective developers. | ||
615 | 620 | ||
616 | == Features | 621 | == Features |
617 | 622 | ||