aboutsummaryrefslogtreecommitdiff
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
* check style for assist docsAleksey Kladov2019-10-261-4/+53
|
* use correct spacing for enum patternAleksey Kladov2019-10-261-1/+1
|
* document a couple of assistsAleksey Kladov2019-10-262-51/+37
|
* generate more assists docsAleksey Kladov2019-10-252-91/+137
|
* sublime: hint where feature flags would goJacob2019-10-251-1/+5
|
* auto-generate assists docs and testsAleksey Kladov2019-10-252-1/+27
|
* document feature flagsAleksey Kladov2019-10-251-2/+11
|
* Update rustdoc link pt.2memoryruins2019-10-241-1/+1
|
* xtask: fold gen-tests and gen-ast into codegenAleksey Kladov2019-10-231-1/+1
|
* Instructions for VSCode RemoteMarco Groppo2019-10-211-0/+19
|
* rename tools -> xtaskAleksey Kladov2019-10-172-6/+6
|
* WIP: move to xtasksAleksey Kladov2019-10-172-13/+7
|
* Adds config option for cargo-watch `--ignore` flagRoberto Vidal2019-10-171-0/+1
|
* Update link to api rustdocsmemoryruins2019-10-141-1/+1
|
* Merge #1922bors[bot]2019-10-081-3/+4
|\ | | | | | | | | | | | | | | 1922: feat(assists): Make raw string unescaped r=matklad a=Geobert Last piece of https://github.com/rust-analyzer/rust-analyzer/issues/1730 Co-authored-by: Geobert Quach <[email protected]>
| * feat(assists): Keep only one version of make_raw_stringGeobert Quach2019-09-291-16/+2
| |
| * feat(assists): Make raw string unescapedGeobert Quach2019-09-261-0/+15
| |
* | use lockfile in cargo installAleksey Kladov2019-10-081-1/+1
| |
* | remove `visitor` moduleEkaterina Babshukova2019-10-052-5/+3
| |
* | Merge #1952bors[bot]2019-10-051-0/+14
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1952: Create an assist for applying De Morgan's Law r=matklad a=cronokirby Fixes #1807 This assist can transform expressions of the form `!x || !y` into `!(x && y)`. This also works with `&&`. This assist will only trigger if the cursor is on the central logical operator. The main limitation of this current implementation is that both operands need to be an explicit negation, either of the form `!x`, or `x != y`. More operands could be accepted, but this would complicate the implementation quite a bit. Co-authored-by: Lúcás Meier <[email protected]>
| * | Fix typo about De Morgan's law assistLúcás Meier2019-10-041-1/+1
| | |
| * | [#1807] Add entry in docs/user/featuresLúcás Meier2019-10-041-0/+14
| |/
* / Add alternative setup instruction for vim/neovimLuke Jones2019-10-041-0/+16
|/ | | | Provide another option hint for vim/neovim users who do not want to run nodejs
* Missing wordnicrd2019-09-261-1/+1
|
* update documentation according to new settingsPaul Lesur2019-09-251-1/+2
| | | | | | | 1. `command` has been added to change the default cargo-watch command 2. `check-arguments` has been renamed to `arguments` as a consequence Thoses changes were merged in #1434
* feat(assists): raw string <-> usual string manipulationGeobert Quach2019-09-191-0/+56
| | | | Fixes #1730
* Fixed markdown in user READMEzoewithabang2019-09-181-1/+1
|
* clarify sublime instructionsAleksey Kladov2019-09-111-1/+3
| | | | closes #1811
* Update README.mdHeyward Fann2019-09-091-1/+1
|
* Update README.mdHeyward Fann2019-09-091-2/+3
| | | fixes base on #1755 reviews
* Merge #1755bors[bot]2019-09-061-27/+4
|\ | | | | | | | | | | | | | | 1755: feat(docs): add coc-rust-analyzer r=JeanMertz a=fannheyward Co-authored-by: Heyward Fann <[email protected]>
| * feat(docs): add coc-rust-analyzerHeyward Fann2019-09-031-27/+4
| |
* | add option to disable notifyAleksey Kladov2019-09-061-0/+2
| |
* | add assist to move type bounds to where clauseEkaterina Babshukova2019-09-051-0/+10
|/
* Make sysroot use `RUST_SRC_PATH` if setBastian Köcher2019-08-221-0/+1
|
* Merge #1663bors[bot]2019-08-071-2/+2
|\ | | | | | | | | | | | | | | 1663: architecture.md: update path to parser tests r=matklad a=eupn Co-authored-by: eupn <[email protected]>
| * architecture.md: update path to parser testseupn2019-08-071-2/+2
| |
* | architecture.md: "finish not Y" -> "finish node Y"eupn2019-08-071-1/+1
|/ | | Is this a typo?
* allow to exclude certain files and directoriesAleksey Kladov2019-08-061-0/+3
|
* document upgrade processAleksey Kladov2019-07-292-0/+5
| | | | closes #1615
* Overhaul installation processAleksey Kladov2019-07-272-6/+6
| | | | | | | The new commands are $ cargo install-ra --client-code $ cargo install-ra --server --jemalloc
* Implement inlay hints for emacsFlorian Diebold2019-07-271-1/+1
|
* fix: spellingMartin Grönlund2019-07-151-1/+1
|
* Remove executeCommandProvider: apply_code_action.Michael Bolin2019-07-111-2/+0
| | | | | | | | | | | | | | | | | | | This appears to have been introduced ages ago in https://github.com/rust-analyzer/rust-analyzer/commit/be742a587704f27f4e503c50f549aa9ec1527fcc but has since been removed. As it stands, it is problematic if multiple instances of the rust-analyzer LSP are launched during the same VS Code session because VS Code complains about multiple LSP servers trying to register the same command. Most LSP servers workaround this by parameterizing the command by the process id. For example, this is where `rls` does this: https://github.com/rust-lang/rls/blob/ff0b9057c8f62bc4f8113d741e96c9587ef1a817/rls/src/server/mod.rs#L413-L421 Though `apply_code_action` does not seems to be used, so it seems better to delete it than to parameterize it.
* Document the VS Code extension test frameworkRyan Cumming2019-06-261-0/+19
|
* More details on how to set up cocWho? Me?!2019-06-181-0/+21
|
* add analysis-bench to benchmark incremental analysisAleksey Kladov2019-06-161-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Can be used like this: ``` $ cargo run --release -p ra_cli -- \ analysis-bench ../chalk/ \ --complete ../chalk/chalk-engine/src/logic.rs:94:0 loading: 225.970093ms from scratch: 8.492373325s no change: 445.265µs trivial change: 95.631242ms ``` Or like this: ``` $ cargo run --release -p ra_cli -- \ analysis-bench ../chalk/ \ --highlight ../chalk/chalk-engine/src/logic.rs loading: 209.873484ms from scratch: 9.504916942s no change: 7.731119ms trivial change: 124.984039ms ``` "from scratch" includes initial analysis of the relevant bits of the project "no change" just asks the same question for the second time. It measures overhead on assembling the answer outside of salsa. "trivial change" doesn't do an actual salsa change, it just advances the revision. This test how fast is salsa at validating things.
* fixed wrong links againzjy2019-06-121-4/+4
|
* fixed linkszjy2019-06-111-5/+5
|
* Fix typo docs/user/README.mdAndrew Chin2019-05-301-1/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-23 17:01:20 +0000