aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
...
| * Implement glob imports within the same crateFlorian Diebold2019-02-101-16/+77
| | | | | | | | Fixes #231.
| * Import glob imports from other cratesFlorian Diebold2019-02-103-2/+17
| | | | | | | | This is the easy part since we don't have to consider the fixpoint algorithm.
| * Implement glob imports from enumsFlorian Diebold2019-02-102-6/+37
| |
| * Add some testsFlorian Diebold2019-02-102-0/+120
| |
* | Merge #762bors[bot]2019-02-102-0/+732
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | 762: "Dumb" auto import assist r=matklad a=eulerdisk This adds a new assist to "add xxx::yyy to the current file" when the cursor is on a PATH. It manages correctly nested imports,`self` keyword and creates new nested imports if necessary. [See the tests] It doesn't use name resolution so in that sense is 'dumb', but I have plans to do that. That in the future will be useful to auto import trait names in autocompletion for example. It can easily be extended to provide multiple actions to select in which scope to import. That's another thing I plan to do. @matklad I copied some indentation code from `ide_light`, I don't know at the moment if/how you want to refactor that code. This assist was meant to be in `ide_light`. Co-authored-by: Andrea Pretto <[email protected]>
| * auto_import: use ra_fmtAndrea Pretto2019-02-091-109/+29
| |
| * auto_import: struct variants for ImportActionAndrea Pretto2019-02-091-44/+107
| |
| * auto_import: remove PathSegmentsMatchAndrea Pretto2019-02-092-66/+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-093-0/+784
| |
* | Spell cases explicitly in Ty::walk{_mut}Florian Diebold2019-02-101-2/+18
| |
* | Clean up a bitFlorian Diebold2019-02-102-9/+1
| |
* | Add a smoke test for ra_batchFlorian Diebold2019-02-101-0/+24
| |
* | Add an ra_cli command that analyses all crates in the current workspaceFlorian Diebold2019-02-108-4/+200
| | | | | | | | ... and prints various stats about how many expressions have a type etc.
* | Implement BatchDatabase constructionFlorian Diebold2019-02-104-14/+113
| |
* | Add new crateFlorian Diebold2019-02-102-0/+54
| |
* | Merge #770bors[bot]2019-02-101-1/+80
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 770: Fix introduce var duplicating newlines r=matklad a=vipentti This fixes #713. If the block before the statement we want to use introduce var on, had empty lines these empty lines would also be added between the let-statement and the current line where the new variable is used. This fixes that by trimming excess newlines from the start of the indent chunk and simply adding a single newline (when the chunk had newlines) between the let-statement and the current statement. If there were no newlines this matches the previous behaviour. Co-authored-by: Ville Penttinen <[email protected]>
| * | Fix introduce var duplicating newlinesVille Penttinen2019-02-091-1/+80
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes #713. If the block before the statement we want to use introduce var on, had empty lines these empty lines would also be added between the let-statement and the current line where the new variable is used. This fixes that by trimming excess newlines from the start of the indent chunk and simply adding a single newline (when the chunk had newlines) between the let-statement and the current statement. If there were no newlines this matches the previous behaviour.
* | | Add comment and markFlorian Diebold2019-02-093-2/+10
| | |
* | | Fix another crash, and try harder to prevent stack overflowsFlorian Diebold2019-02-093-7/+75
| | |
* | | Fix another crash found when analyzing rustcFlorian Diebold2019-02-093-7/+38
| | |
* | | Fix handling of literal patternsFlorian Diebold2019-02-0910-41/+133
| | | | | | | | | | | | | | | Wrap them in a LiteralPat node so they can be distinguished from literal expressions.
* | | Fix two crashes found by running inference on all of rustcFlorian Diebold2019-02-094-15/+84
| | |
* | | update notify with fix for hight cpu usageBernardo2019-02-091-1/+1
|/ /
* | Clean up a bitFlorian Diebold2019-02-092-3/+1
| |
* | Remove Vfs from project modelFlorian Diebold2019-02-093-8/+8
| |
* | Remove SmolStr from project modelFlorian Diebold2019-02-094-18/+7
| |
* | Move crate graph generation to ra_project_modelFlorian Diebold2019-02-094-83/+113
| |
* | Extract project model to separate crateFlorian Diebold2019-02-097-52/+94
|/
* Merge #766bors[bot]2019-02-099-9/+23
|\ | | | | | | | | | | | | | | | | | | 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-089-9/+23
| |
* | 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-085-10/+58
|/
* reformat the worldAleksey Kladov2019-02-08129-2510/+728
|
* 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
|
* 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.
* Some clippy cleanupskjeremy2019-02-0615-55/+49
|
* assists: compute editkjeremy2019-02-061-1/+1
|
* move assists to a separate crateAleksey Kladov2019-02-0625-580/+568
|
* Remove stray dbg!Jeremy Kolb2019-02-061-1/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-14 21:41:58 +0000