aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* auto_import: remove PathSegmentsMatchAndrea Pretto2019-02-093-67/+37
|
* auto_import: Removed Empty in favor of Partial(0)Andrea Pretto2019-02-091-16/+10
| | | | auto_import: Removed unecessary lifetimes
* auto_import assistAndrea Pretto2019-02-094-0/+785
|
* Merge #766bors[bot]2019-02-0910-10/+33
|\ | | | | | | | | | | | | | | | | | | 766: Formatting code into ra_fmt r=matklad a=eulerdisk As discussed https://github.com/rust-analyzer/rust-analyzer/pull/762#discussion_r254905885 I did only move the code without other improvements. Co-authored-by: Andrea Pretto <[email protected]>
| * Refactor formatting code out of ra_ida_api_light into ra_fmt.Andrea Pretto2019-02-0810-10/+33
| |
* | Merge #768bors[bot]2019-02-0912-22/+264
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | 768: Sort assists by the range of the affected element r=matklad a=robojumper Closes #763. https://github.com/rust-analyzer/rust-analyzer/blob/3be98f2ac93b278828e76eb813bdd8033f647b12/crates/ra_assists/src/lib.rs#L233-L236 This could be made more robust by a) adding a way to identify actions by things other than their label and b) allowing arbitrary actions to appear in the list as long as the tested actions are there in the correct order. Let me know if I should do any of that. Co-authored-by: robojumper <[email protected]>
| * Improve sorting delegaterobojumper2019-02-091-7/+5
| |
| * Remove unused importrobojumper2019-02-081-2/+2
| |
| * Add tests for action target rangesrobojumper2019-02-0810-16/+210
| |
| * Add some assist rangesrobojumper2019-02-086-10/+60
|/
* reformat the worldAleksey Kladov2019-02-08129-2510/+728
|
* enable "small heuristics"Aleksey Kladov2019-02-081-1/+2
|
* Merge #765bors[bot]2019-02-0811-441/+428
|\ | | | | | | | | | | | | | | 765: Jettison `imp` module r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * diagnostics is now a functionAleksey Kladov2019-02-082-64/+62
| |
| * move diagnostics to a separate fileAleksey Kladov2019-02-082-27/+22
| |
| * move index_resolve to symbol indexAleksey Kladov2019-02-084-14/+11
| |
| * move find_references to referencesAleksey Kladov2019-02-083-67/+55
| |
| * avoid 'ignored' in test outputAleksey Kladov2019-02-081-2/+2
| |
| * rename rename to referencesAleksey Kladov2019-02-082-2/+2
| |
| * move crate forAleksey Kladov2019-02-083-16/+16
| |
| * move changes to a separate fileAleksey Kladov2019-02-084-254/+263
|/
* Merge #760bors[bot]2019-02-072-0/+125
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 760: Add new assist to remove dbg!() calls r=matklad a=vipentti This fixes #758. Currently we try to maintain the cursor position relative to the statement under cursor, if the cursor is inside the dbg! macro call. Meaning: ```rust let foo = dbg!(some.complex<|>().expression()); ``` Should turn into: ```rust let foo = some.complex<|>().expression(); ``` With the cursor staying in place. Co-authored-by: Ville Penttinen <[email protected]>
| * Remove unnecessary dbg! callsVille Penttinen2019-02-071-3/+2
| |
| * Add new assist to remove dbg!() callsVille Penttinen2019-02-072-0/+126
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes #758. Currently we try to maintain the cursor position relative to the statement under cursor, if the cursor is inside the dbg! macro call. Meaning: let foo = dbg!(some.complex<|>().expression()); Should turn into: let foo = some.complex<|>().expression(); With the cursor staying in place.
* | Merge #761bors[bot]2019-02-072-99/+65
|\ \ | |/ |/| | | | | | | | | | | 761: Update npm packages r=matklad a=kjeremy Co-authored-by: kjeremy <[email protected]>
| * Update npm packageskjeremy2019-02-072-99/+65
|/
* Merge #755bors[bot]2019-02-073-1/+40
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 755: Add new configuration "enableEnhancedTyping" to control registering of "type" command r=matklad a=vipentti This further fixes problems when having a VIM extension (at least vscodevim) enabled, by not calling `overrideCommand('type', commands.onEnter.handle)` when enableEnhancedTyping is set to `false`. The problem is dependent on the order in which extensions are activated, if rust-analyzer is activated before `vscodevim`, rust-analyzer will register the `type` command, and when `vscodevim` finally attempts to activate, it will fail to register the command. This causes `vscodevim` to stop working properly. This setting allows users to disable the registerCommand `type` in rust-analyzer, allowing `vscodevim` to work. The setting defaults to `true`. Currently changing the setting requires reloading of the window. Co-authored-by: Ville Penttinen <[email protected]>
| * Run prettierVille Penttinen2019-02-071-4/+11
| |
| * Add new configuration "enableEnhancedTyping" to control registering of ↵Ville Penttinen2019-02-073-1/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "type" command This further fixes problems when having a VIM extension (at least vscodevim) enabled, by not calling `overrideCommand('type', commands.onEnter.handle)` when enableEnhancedTyping is set to `false`. The problem is dependent on the order in which extensions are activated, if rust-analyzer is activated before `vscodevim`, rust-analyzer will register the `type` command, and when `vscodevim` finally attempts to activate, it will fail to register the command. This causes `vscodevim` to stop working properly. This setting allows users to disable the registerCommand `type` in rust-analyzer, allowing `vscodevim` to work. The setting defaults to `true`. Currently changing the setting requires reloading of the window.
* | Merge #754bors[bot]2019-02-0615-55/+49
|\ \ | | | | | | | | | | | | | | | | | | | | | 754: Some clippy things r=matklad a=kjeremy Co-authored-by: kjeremy <[email protected]>
| * | Some clippy cleanupskjeremy2019-02-0615-55/+49
|/ /
* | Merge #753bors[bot]2019-02-061-1/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | 753: assists: compute edit r=matklad a=kjeremy Fixes #751 Co-authored-by: kjeremy <[email protected]>
| * | assists: compute editkjeremy2019-02-061-1/+1
|/ /
* | Merge #752bors[bot]2019-02-061-73/+14
|\ \ | | | | | | | | | | | | | | | | | | | | | 752: cargo update r=kjeremy a=kjeremy Removes a few crates from the dep chain. Co-authored-by: kjeremy <[email protected]>
| * | cargo updatekjeremy2019-02-061-73/+14
|/ /
* | Merge #750bors[bot]2019-02-0626-580/+582
|\ \ | |/ |/| | | | | | | | | | | | | | | 750: Move assists to a separate crate r=matklad a=matklad I am slowly coming to conclusion that ide_api_light does not make a lot of sense after all :D This PR moves assists to a separate crate, so that assists can use database (so, inspect types, do name-resolution, etc) Co-authored-by: Aleksey Kladov <[email protected]>
| * move assists to a separate crateAleksey Kladov2019-02-0626-580/+582
|/
* Merge #748bors[bot]2019-02-066-23/+86
|\ | | | | | | | | | | | | | | | | 748: Fill deprecation for LSP r=kjeremy a=kjeremy Co-authored-by: kjeremy <[email protected]> Co-authored-by: Jeremy Kolb <[email protected]>
| * Remove stray dbg!Jeremy Kolb2019-02-061-1/+1
| |
| * Fill deprecation for LSPkjeremy2019-02-056-23/+86
|/
* Merge #746bors[bot]2019-02-056-5/+5
|\ | | | | | | | | | | | | | | 746: Rename assits to assists r=kjeremy a=kjeremy Co-authored-by: Jeremy Kolb <[email protected]>
| * Rename assits to assistsJeremy Kolb2019-02-056-5/+5
|/
* Merge #740bors[bot]2019-02-057-112/+129
|\ | | | | | | | | | | | | | | | | 740: Update dependencies r=kjeremy a=kjeremy Co-authored-by: kjeremy <[email protected]> Co-authored-by: Jeremy Kolb <[email protected]>
| * Remove unused importsJeremy Kolb2019-02-052-2/+2
| |
| * Bump insta and proptest to latestkjeremy2019-02-045-28/+37
| |
| * cargo updatekjeremy2019-02-041-92/+100
| |
* | Merge #742bors[bot]2019-02-0514-48/+190
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | 742: Extern crate r=matklad a=flodiebold This implements `extern crate` declarations by lowering them to (absolute) imports, and adds support for absolute paths. It also extracts the extern prelude from the per-module item map, and handles the special case of extern crates in the crate root adding to the extern prelude. This means we finally resolve `Arc`, so it fixes #523 :smile: Co-authored-by: Florian Diebold <[email protected]>
| * | Fix ReachedFixedPoint value for unresolved external prelude itemsFlorian Diebold2019-02-041-1/+1
| | |
| * | Complete extern prelude (again)Florian Diebold2019-02-044-2/+41
| | |
| * | Make it possible to have multiple crate in a mock analysis fixtureFlorian Diebold2019-02-041-2/+10
| | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 10:27:50 +0000