aboutsummaryrefslogtreecommitdiff
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
* Update docs/user/manual.adocAleksey Kladov2021-03-221-1/+1
| | | Co-authored-by: bjorn3 <[email protected]>
* Document our security stanceAleksey Kladov2021-03-221-0/+14
| | | | changelog: feature
* Update docs/user/manual.adocAleksey Kladov2021-03-181-1/+1
|
* Update info about Eclipse CorrosionMickael Istria2021-03-181-4/+2
|
* Prefer match to if let elseAleksey Kladov2021-03-161-0/+21
|
* Enable proc-macros by defaultAleksey Kladov2021-03-151-1/+1
|
* Fix `cargo xtask lint` referencesLaurențiu Nicola2021-03-141-2/+2
|
* Merge #7799bors[bot]2021-03-131-1/+17
|\ | | | | | | | | | | | | | | | | | | | | | | | | 7799: Related tests r=matklad a=vsrs ![tests](https://user-images.githubusercontent.com/62505555/109397453-a9013680-7947-11eb-8b11-ac03079f7645.gif) This adds an ability to look for tests for the item under the cursor: function, constant, data type, etc The LSP part is bound to change. But the feature itself already works and I'm looking for a feedback :) Co-authored-by: vsrs <[email protected]>
| * Fix LSP extensions documentationvsrs2021-03-111-7/+2
| |
| * Update lsp-extensions.mdvsrs2021-02-271-1/+22
| |
* | Fix remaining references to `cargo xtask codegen`Lukas Wirth2021-03-122-4/+4
| |
* | Make code less surprisingAleksey Kladov2021-03-091-57/+265
| | | | | | | | Theres no reason to have literal `\n\n` in the source code
* | Merge #7927bors[bot]2021-03-091-1/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | 7927: Add more documentation for rustc_private r=matklad a=jyn514 Co-authored-by: Joshua Nelson <[email protected]>
| * | Add more documentation for rustc_privateJoshua Nelson2021-03-081-1/+1
| | |
* | | Clarify that all caps are experimentalAleksey Kladov2021-03-091-10/+10
|/ /
* | Use upstream cov-markLaurențiu Nicola2021-03-081-1/+1
| |
* | Hygiene is an internal implementation detail of the compilerAleksey Kladov2021-03-081-1/+1
| |
* | Make `code generation` just workAleksey Kladov2021-03-081-2/+1
| | | | | | | | | | Contributors don't need to learn about `cargo xtask codegen` if `cargo test` just does the right thing.
* | Merge #7891bors[bot]2021-03-081-1/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7891: Improve handling of rustc_private r=matklad a=DJMcNab This PR changes how `rust-analyzer` handles `rustc_private`. In particular, packages now must opt-in to using `rustc_private` in `Cargo.toml`, by adding: ```toml [package.metadata.rust-analyzer] rustc_private=true ``` This means that depending on crates which also use `rustc_private` will be significantly improved, since their dependencies on the `rustc_private` crates will be resolved properly. A similar approach could be used in #6714 to allow annotating that your package uses the `test` crate, although I have not yet handled that in this PR. Additionally, we now only index the crates which are transitive dependencies of `rustc_driver` in the `rustcSource` directory. This should not cause any change in behaviour when using `rustcSource: "discover"`, as the source used then will only be a partial clone. However, if `rustcSource` pointing at a local checkout of rustc, this should significantly improve the memory usage and lower indexing time. This is because we avoids indexing all crates in `src/tools/`, which includes `rust-analyzer` itself. Furthermore, we also prefer named dependencies over dependencies from `rustcSource`. This ensures that feature resolution for crates which are depended on by both `rustc` and your crate uses the correct set for analysing your crate. See also [introductory zulip stream](https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0/topic/Fixed.20crate.20graphs.20and.20optional.20builtin.20crates/near/229086673) I have tested this in [priroda](https://github.com/oli-obk/priroda/), and it provides a significant improvement to the development experience (once I give `miri` the required data in `Cargo.toml`) Todo: - [ ] Documentation This is ready to review, and I will add documentation if this would be accepted (or if I get time to do so anyway) Co-authored-by: Daniel McNab <[email protected]>
| * | Document rustc_private in metadataDaniel McNab2021-03-081-1/+1
| | |
| * | Revert "Support disabling rustc build scripts"Daniel McNab2021-03-081-2/+0
| | | | | | | | | | | | This reverts commit ddce6bb282764692d53b719bff4c37e3512d4556.
| * | Support disabling rustc build scriptsDaniel McNab2021-03-081-0/+2
| | |
* | | Make code completion "just work" in more casesAleksey Kladov2021-03-081-1/+1
| | |
* | | Merge #7889bors[bot]2021-03-071-0/+2
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 7889: Make group imports configurable r=lnicola a=asv1 Co-authored-by: asv <[email protected]>
| * | Make group imports configurableasv2021-03-071-0/+2
| | |
* | | Add a line about code action commands to the CoC section of the docsFlorian Diebold2021-03-061-0/+2
|/ /
* | Merge #7868bors[bot]2021-03-041-3/+3
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | 7868: Migrate to user-centric config name for `cargo check` stuff r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | Migrate to user-centric config name for `cargo check` stuffAleksey Kladov2021-03-041-3/+3
| | |
* | | Clarify comparison ruleAleksey Kladov2021-03-031-1/+7
|/ /
* | Axe pre-commitAleksey Kladov2021-03-011-2/+0
| |
* | Fixed remaining references to `AnalysisChange` (now: `Change`)Vincent Esche2021-02-281-5/+5
|/ | | | (The type was renamed/moved in 8716c4cec3a05ba891b20b5f28df69d925b913ad)
* Fix typo.boxdot2021-02-241-1/+1
|
* Fix typosazzamsa2021-02-202-6/+6
|
* document offsetsAleksey Kladov2021-02-161-1/+7
|
* Merge #7643 #7663bors[bot]2021-02-141-1/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7643: Automatically detect the rustc-src directory (fixes #3517) r=matklad a=bnjbvr If the configured rustcSource was not set, then try to automatically detect a source for the sysroot rustc directory. I wasn't sure how to do it in the case of the project.json file, though. 7663: Tolerate spaces in nix binary patching r=matklad a=CertainLach If path to original file contains space (I.e on code insiders, where default data directory is ~/Code - Insiders/), then there is syntax error evaluating src arg. Instead pass path as str, and coerce to path back in nix expression Co-authored-by: Benjamin Bouvier <[email protected]> Co-authored-by: Yaroslav Bolyukin <[email protected]>
| * Allow automatically detect the rustc-src directory (fixes #3517).Benjamin Bouvier2021-02-131-1/+1
| | | | | | | | | | If the configured rustcSource is set to "discover", try to automatically detect a source from the sysroot rustc directory.
* | Remove CodeLensResolveData mention from lsp-extensions.mdivan7702021-02-131-11/+0
| |
* | Moved CodeLens to ide crateivan7702021-02-131-1/+12
|/
* Include a commit log summary in the changelogLaurențiu Nicola2021-02-121-2/+1
|
* Merge #7653bors[bot]2021-02-121-0/+60
|\ | | | | | | | | | | | | | | | | 7653: Document config pattern r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * Document config patternAleksey Kladov2021-02-121-0/+60
| |
* | fix nightly warning `legacy_derive_helpers`Peter Wischer2021-02-121-1/+1
|/ | | | see https://github.com/rust-lang/rust/issues/79202
* Use track caller in test documentationAleksey Kladov2021-02-101-1/+1
|
* Infra for "unit" benchmarkingAleksey Kladov2021-02-091-0/+5
|
* Add emacs guideAleksey Kladov2021-02-081-0/+2
|
* Merge #7592bors[bot]2021-02-081-0/+10
|\ | | | | | | | | | | | | | | 7592: [Doc] Note about Eclipse IDE support r=lnicola a=mickaelistria Co-authored-by: Mickael Istria <[email protected]>
| * [Doc] Note about Eclipse IDE supportMickael Istria2021-02-081-0/+10
| |
* | Vim docs: vim-lsp with initial configuration.Ilya Bobyr2021-02-081-0/+46
| | | | | | | | | | | | `vim-lsp` is another popular LSP client for Vim. And, as there is no `rust-analyzer` specific UI, it is non-trivial to figure out how the initial configuration is performed.
* | Explain how initial configuration is sent over LSP.Ilya Bobyr2021-02-081-5/+27
|/
* Add a section on entry pointsAleksey Kladov2021-02-071-1/+9
|