| /third_party/rust/rust/src/tools/rust-analyzer/docs/user/ |
| D | generated_config.adoc | 1 [[rust-analyzer.assist.emitMustUse]]rust-analyzer.assist.emitMustUse (default: `false`)::
3 --
6 --
7 [[rust-analyzer.assist.expressionFillDefault]]rust-analyzer.assist.expressionFillDefault (default: …
9 --
11 --
12 [[rust-analyzer.cachePriming.enable]]rust-analyzer.cachePriming.enable (default: `true`)::
14 --
16 --
17 [[rust-analyzer.cachePriming.numThreads]]rust-analyzer.cachePriming.numThreads (default: `0`)::
[all …]
|
| D | manual.adoc | 4 :page-layout: post
6 :source-highlighter: rouge
10 IMPORTANT: the master copy of this document lives in the https://github.com/rust-lang/rust-analyzer…
13 At its core, rust-analyzer is a *library* for semantic analysis of Rust code as it changes over tim…
14 This manual focuses on a specific usage of the library -- running it as part of a server that imple…
15 https://microsoft.github.io/language-server-protocol/[Language Server Protocol] (LSP).
22 https://github.com/rust-lang/rust-analyzer/blob/master/docs/user/manual.adoc[https://github.com/rus…
24 … which are generated from the source code. Run `cargo test` and `cargo test -p xtask` to create th…
27 …uestions about using rust-analyzer, please ask them in the https://users.rust-lang.org/c/ide/14["`…
31 …n theory, one should be able to just install the <<rust-analyzer-language-server-binary,`rust-anal…
[all …]
|
| /third_party/rust/rust/src/tools/rust-analyzer/editors/code/ |
| D | package.json | 2 "name": "rust-analyzer",
3 "displayName": "rust-analyzer",
4 "description": "Rust language support for Visual Studio Code",
7 "version": "0.5.0-dev",
9 "publisher": "rust-lang",
11 "url": "https://github.com/rust-lang/rust-analyzer.git",
14 "homepage": "https://rust-analyzer.github.io/",
15 "license": "MIT OR Apache-2.0",
17 "rust"
25 …"description": "rust-analyzer invokes binaries set up by its configuration as well as the Rust too…
[all …]
|
| D | README.md | 1 # rust-analyzer chapter
3 This extension provides support for the [Rust programming language](https://www.rust-lang.org/).
4 It is recommended over and replaces `rust-lang.rust`.
8 - [code completion] with [imports insertion]
9 - go to [definition], [implementation], [type definition]
10 - [find all references], [workspace symbol search], [symbol renaming]
11 - [types and documentation on hover]
12 - [inlay hints] for types and parameter names
13 - [semantic syntax highlighting]
14 - a lot of [assists (code actions)]
[all …]
|
| /third_party/rust/rust/src/tools/rust-analyzer/docs/dev/ |
| D | README.md | 3 rust-analyzer is an ordinary Rust project, which is organized as a Cargo workspace, builds on stabl…
12 To learn more about how rust-analyzer works, see [./architecture.md](./architecture.md).
13 It also explains the high-level layout of the source code.
16 We also publish rustdoc docs to pages: https://rust-lang.github.io/rust-analyzer/ide/.
23 rust-analyzer is a part of the [RLS-2.0 working
24 group](https://github.com/rust-lang/compiler-team/tree/6a769c13656c0a6959ebc09e7b1f7c09b86fb9c0/wor…
27 https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frust-analyzer
31 * [good-first-issue](https://github.com/rust-lang/rust-analyzer/labels/good%20first%20issue)
33 * [E-has-instructions](https://github.com/rust-lang/rust-analyzer/issues?q=is%3Aopen+is%3Aissue+lab…
35 * [Broken Window](https://github.com/rust-lang/rust-analyzer/issues?q=is:issue+is:open+label:%22Bro…
[all …]
|
| D | guide.md | 1 # Guide to rust-analyzer
5 This guide describes the current state of rust-analyzer as of 2019-01-20 (git
6 tag [guide-2019-01]). Its purpose is to document various problems and
7 architectural solutions related to the problem of building IDE-first compiler
8 for Rust. There is a video version of this guide as well:
11 [guide-2019-01]: https://github.com/rust-lang/rust-analyzer/tree/guide-2019-01
15 On the highest possible level, rust-analyzer is a stateful component. A client may
16 apply changes to the analyzer (new contents of `foo.rs` file is "fn main() {}")
21 * Analyzer does not do any I/O. It starts in an empty state and all input data is
39 terms of files and offsets, and **not** in terms of Rust concepts like structs,
[all …]
|
| D | architecture.md | 3 This document describes the high-level architecture of rust-analyzer.
6 You might also enjoy ["Explaining Rust Analyzer"](https://www.youtube.com/playlist?list=PLhb66M_x9U…
9 See also these implementation-related blog posts:
11 * https://rust-analyzer.github.io/blog/2019/11/13/find-usages.html
12 * https://rust-analyzer.github.io/blog/2020/07/20/three-architectures-for-responsive-ide.html
13 * https://rust-analyzer.github.io/blog/2020/09/16/challeging-LR-parsing.html
14 * https://rust-analyzer.github.io/blog/2020/09/28/how-to-make-a-light-bulb.html
15 * https://rust-analyzer.github.io/blog/2020/10/24/introducing-ungrammar.html
17 …) and [another playlist](https://www.youtube.com/playlist?list=PL85XCvVPmGQho7MZkdW-wtPtuJcFpzycE).
22  and the [LLDB Extension](https://marketplace.visualstudio.…
6 - Open the root folder in VSCode. Here you can access the preconfigured debug setups.
8 …<img height=150px src="https://user-images.githubusercontent.com/36276403/74611090-92ec5380-5101-1…
10 - Install all TypeScript dependencies
19 where **only** the `rust-analyzer` extension being debugged is enabled.
20 * To activate the extension you need to open any Rust project folder in `[Extension Development Hos…
25 - `Run Installed Extension` - runs the extension with the globally installed `rust-analyzer` binary.
26 - `Run Extension (Debug Build)` - runs extension with the locally built LSP server (`target/debug/r…
35 ## Debug Rust LSP server
37 - When attaching a debugger to an already running `rust-analyzer` server on Linux you might need to…
[all …]
|
| D | lsp-extensions.md | 1 <!---
7 https://github.com/rust-lang/rust-analyzer/issues/4604
9 --->
13 This document describes LSP extensions used by rust-analyzer.
14 It's a best effort document, when in doubt, consult the source (and send a PR with clarification ;-…
15 We aim to upstream all non Rust-specific extensions to the protocol, but this is not a top priority.
18 Requests, which are likely to always remain specific to `rust-analyzer` are under `rust-analyzer/` …
20 …hanges to this document, subscribe to [#4604](https://github.com/rust-lang/rust-analyzer/issues/46…
24 **Upstream Issue:** https://github.com/microsoft/language-server-protocol/issues/567
26 …`InitializeParams` of the initialization request should contain the `"rust-analyzer"` section of t…
[all …]
|
| /third_party/rust/rust/src/tools/rust-analyzer/ |
| D | README.md | 3 src="https://raw.githubusercontent.com/rust-analyzer/rust-analyzer/master/assets/logo-wide.svg"
4 alt="rust-analyzer logo">
7 rust-analyzer is a modular compiler frontend for the Rust language.
8 It is a part of a larger rls-2.0 effort to create excellent IDE support for Rust.
12 https://rust-analyzer.github.io/manual.html#installation
16 If you want to **contribute** to rust-analyzer or are just curious about how
19 If you want to **use** rust-analyzer's language server with your editor of
20 choice, check [the manual](https://rust-analyzer.github.io/manual.html) folder.
21 It also contains some tips & tricks to help you be more productive when using rust-analyzer.
25 See the corresponding sections of [the manual](https://rust-analyzer.github.io/manual.html#security…
[all …]
|
| /third_party/rust/rust/src/etc/ |
| D | rust_analyzer_settings.json | 2 "rust-analyzer.check.invocationLocation": "root",
3 "rust-analyzer.check.invocationStrategy": "once",
4 "rust-analyzer.check.overrideCommand": [
8 "--json-output"
10 "rust-analyzer.linkedProjects": [
14 "src/tools/rust-analyzer/Cargo.toml",
18 "rust-analyzer.rustfmt.overrideCommand": [
20 "--edition=2021"
22 "rust-analyzer.procMacro.server": "./build/host/stage0/libexec/rust-analyzer-proc-macro-srv",
23 "rust-analyzer.procMacro.enable": true,
[all …]
|
| /third_party/rust/rust/src/tools/rust-analyzer/editors/code/src/ |
| D | lsp_ext.ts | 2 * This file mirrors `crates/rust-analyzer/src/lsp_ext.rs` declarations.
5 import * as lc from "vscode-languageclient";
7 // rust-analyzer overrides
27 // rust-analyzer extensions
30 "rust-analyzer/analyzerStatus"
32 export const cancelFlycheck = new lc.NotificationType0("rust-analyzer/cancelFlycheck");
33 export const clearFlycheck = new lc.NotificationType0("rust-analyzer/clearFlycheck");
35 "rust-analyzer/expandMacro"
37 export const memoryUsage = new lc.RequestType0<string, void>("rust-analyzer/memoryUsage");
38 export const openServerLogs = new lc.NotificationType0("rust-analyzer/openServerLogs");
[all …]
|
| D | ctx.ts | 2 import * as lc from "vscode-languageclient/node";
31 // (r-a still somewhat works with Live Share, because commands are tunneled to the host)
169 this.traceOutputChannel = new LazyOutputChannel("Rust Analyzer Language Server Trace");
173 this.outputChannel = vscode.window.createOutputChannel("Rust Analyzer Language Server");
183 … 'See the logs in "OUTPUT > Rust Analyzer Client" (should open automatically). ';
185 'To enable verbose logs use { "rust-analyzer.trace.extension": true }';
201 let rawInitializationOptions = vscode.workspace.getConfiguration("rust-analyzer");
319 …// FIXME: We should re-use the client, that is ctx.deactivate() if none of the configs have changed
388 const fullName = `rust-analyzer.${name}`;
398 `command ${fullName} failed: rust-analyzer server is not running`
[all …]
|
| D | bootstrap.ts | 16 "Rust Analyzer Language Server is not available. " +
17 …"Please, ensure its [proper installation](https://rust-analyzer.github.io/manual.html#installation…
25 …throw new Error(`Failed to execute ${path} --version. \`config.server.path\` or \`config.serverPat…
28 throw new Error(`Failed to execute ${path} --version`);
46 if (config.package.releaseTag === null) return "rust-analyzer";
49 const bundled = vscode.Uri.joinPath(context.extensionUri, "server", `rust-analyzer${ext}`);
58 const dest = vscode.Uri.joinPath(config.globalStorageUri, `rust-analyzer${ext}`);
80 "You need to manually clone the rust-analyzer repository and " +
81 "run `cargo xtask install --server` to build the language server from sources. " +
83 "about that [here](https://github.com/rust-lang/rust-analyzer/issues) and we " +
[all …]
|
| /third_party/rust/rust/src/tools/rust-analyzer/.github/workflows/ |
| D | release.yaml | 4 - cron: "0 0 * * *" # midnight UTC
10 - release
11 - trigger-nightly
16 RUSTFLAGS: "-D warnings -W unreachable-pub"
20 CARGO_TARGET_AARCH64_UNKNOWN_LINUX_GNU_LINKER: aarch64-linux-gnu-gcc
21 CARGO_TARGET_ARM_UNKNOWN_LINUX_GNUEABIHF_LINKER: arm-linux-gnueabihf-gcc
28 - os: windows-latest
29 target: x86_64-pc-windows-msvc
30 code-target: win32-x64
31 - os: windows-latest
[all …]
|
| D | ci.yaml | 1 # Please make sure that the `needs` fields for both `end-success` and `end-failure`
9 - auto
10 - try
17 RUSTFLAGS: "-D warnings -W unreachable-pub -W bare-trait-objects"
22 runs-on: ubuntu-latest
24 pull-requests: read
29 - uses: actions/checkout@v3
30 - uses: dorny/paths-filter@4067d885736b84de7c414f582ac45897079b0a78
35 - 'editors/code/**'
37 - 'crates/proc-macro-api/**'
[all …]
|
| /third_party/rust/crates/syn/tests/repo/ |
| D | mod.rs | 24 "src/tools/rust-analyzer/crates/parser/test_data/parser/inline/ok/0085_expr_literals.rs",
28 "tests/ui/explicit-tail-calls/return-lifetime-sub.rs",
30 // TODO: non-lifetime binders: `where for<'a, T> &'a Struct<T>: Trait`
33 "src/tools/rustfmt/tests/source/non-lifetime-binders.rs",
35 "src/tools/rustfmt/tests/target/non-lifetime-binders.rs",
36 "tests/rustdoc-json/non_lifetime_binders.rs",
42 …"src/tools/rust-analyzer/crates/parser/test_data/parser/inline/ok/0208_associated_return_type_boun…
43 "tests/ui/associated-type-bounds/return-type-notation/basic.rs",
44 "tests/ui/feature-gates/feature-gate-return_type_notation.rs",
46 // TODO: lazy type alias syntax with where-clause in trailing position
[all …]
|
| /third_party/rust/rust/src/tools/rust-analyzer/xtask/test_data/ |
| D | expected.md | 5 Commit: [`0123456`](https://github.com/rust-analyzer/rust-analyzer/commit/0123456789abcdef012345678…
6 Release: [`2022-01-01`](https://github.com/rust-analyzer/rust-analyzer/releases/2022-01-01)
10 - **BREAKING** [`#1111`](https://github.com/rust-analyzer/rust-analyzer/pull/1111) shortcut <kbd>ct…
11 - hyphen-prefixed list item
12 - nested list item
13 - `foo` -> `foofoo`
14 - `bar` -> `barbar`
15 - listing in the secondary level
22 - list item with continuation
45 - single line item followed by empty lines
[all …]
|
| /third_party/rust/rust/compiler/rustc_codegen_cranelift/.vscode/ |
| D | settings.json | 4 // source for rustc_* is not included in the rust-src component; disable the errors about this
5 "rust-analyzer.diagnostics.disabled": ["unresolved-extern-crate", "unresolved-macro-call"],
6 "rust-analyzer.imports.granularity.enforce": true,
7 "rust-analyzer.imports.granularity.group": "module",
8 "rust-analyzer.imports.prefix": "crate",
9 "rust-analyzer.cargo.features": ["unstable-features"],
10 "rust-analyzer.linkedProjects": [
|
| /third_party/rust/rust/src/tools/rust-analyzer/crates/rust-analyzer/src/ |
| D | lsp_ext.rs | 1 //! rust-analyzer extensions to the LSP.
21 const METHOD: &'static str = "rust-analyzer/analyzerStatus";
42 const METHOD: &'static str = "rust-analyzer/fetchDependencyList";
60 const METHOD: &'static str = "rust-analyzer/memoryUsage";
68 const METHOD: &'static str = "rust-analyzer/shuffleCrateGraph";
76 const METHOD: &'static str = "rust-analyzer/reloadWorkspace";
84 const METHOD: &'static str = "rust-analyzer/rebuildProcMacros";
92 const METHOD: &'static str = "rust-analyzer/syntaxTree";
107 const METHOD: &'static str = "rust-analyzer/viewHir";
115 const METHOD: &'static str = "rust-analyzer/viewMir";
[all …]
|
| /third_party/rust/rust/src/tools/rust-analyzer/xtask/src/ |
| D | release.rs | 8 pub(crate) fn run(self, sh: &Shell) -> anyhow::Result<()> { in run()
11 cmd!(sh, "git fetch upstream --tags --force").run()?; in run()
12 cmd!(sh, "git reset --hard tags/nightly").run()?; in run()
13 // The `release` branch sometimes has a couple of cherry-picked in run()
15 // it. As we are setting `release` branch to an up-to-date `nightly` in run()
19 // commits -- they'll be kept alive by the tag. More generally, we in run()
22 cmd!(sh, "git push --force").run()?; in run()
26 cmd!(sh, "cargo test -p ide-assists -p ide-diagnostics -p rust-analyzer -- sourcegen_") in run()
29 let website_root = project_root().join("../rust-analyzer.github.io"); in run()
38 let commit = cmd!(sh, "git rev-parse HEAD").read()?; in run()
[all …]
|
| /third_party/rust/rust/src/tools/rust-analyzer/crates/rust-analyzer/ |
| D | Cargo.toml | 2 name = "rust-analyzer"
4 homepage = "https://github.com/rust-analyzer/rust-analyzer"
5 description = "A language server for the Rust programming language"
6 documentation = "https://rust-analyzer.github.io/manual.html"
12 rust-version.workspace = true
18 name = "rust-analyzer"
23 crossbeam-channel = "0.5.5"
27 lsp-types = { version = "=0.94", features = ["proposed"] }
31 rustc-hash = "1.1.0"
36 mimalloc = { version = "0.1.30", default-features = false, optional = true }
[all …]
|
| /third_party/rust/rust/src/tools/miri/ |
| D | CONTRIBUTING.md | 9 look for the green `E-*` labels which mark issues that should be rather
10 well-suited for onboarding. For more ideas or help with hacking on Miri, you can
11 contact us (`oli-obk` and `RalfJ`) on the [Rust Zulip].
13 [Rust Zulip]: https://rust-lang.zulipchat.com
21 The `rust-version` file contains the commit hash of rustc that Miri is currently
23 [`rustup-toolchain-install-master`], you can run the following command to
31 You can also create a `.auto-everything` file (contents don't matter, can be empty), which
33 for you. If you don't want all of these to happen, you can add individual `.auto-toolchain`,
34 `.auto-clippy` and `.auto-fmt` files respectively.
36 [`rustup-toolchain-install-master`]: https://github.com/kennytm/rustup-toolchain-install-master
[all …]
|
| /third_party/rust/rust/src/tools/rust-analyzer/.github/ISSUE_TEMPLATE/ |
| D | bug_report.md | 1 ---
3 about: Create a bug report for rust-analyzer.
5 labels: 'C-bug'
8 ---
10 <!--
11 Troubleshooting guide: https://rust-analyzer.github.io/manual.html#troubleshooting
12 Forum for questions: https://users.rust-lang.org/c/ide/14
16 …1. on-the-fly diagnostics are mostly unimplemented (`cargo check` diagnostics will be shown when s…
19 -->
21 **rust-analyzer version**: (eg. output of "rust-analyzer: Show RA Version" command, accessible in V…
[all …]
|
| /third_party/rust/rust/src/tools/clippy/ |
| D | CONTRIBUTING.md | 13 All contributors are expected to follow the [Rust Code of Conduct].
15 - [Contributing to Clippy](#contributing-to-clippy)
16 - [The Clippy book](#the-clippy-book)
17 - [High level approach](#high-level-approach)
18 - [Finding something to fix/improve](#finding-something-to-fiximprove)
19 …- [Getting code-completion for rustc internals to work](#getting-code-completion-for-rustc-interna…
20 - [IntelliJ Rust](#intellij-rust)
21 - [Rust Analyzer](#rust-analyzer)
22 - [How Clippy works](#how-clippy-works)
23 - [Issue and PR triage](#issue-and-pr-triage)
[all …]
|