aboutsummaryrefslogtreecommitdiff
path: root/crates/ide_completion
Commit message (Collapse)AuthorAgeFilesLines
* Complete modules in assoc item listsLukas Wirth2021-05-273-5/+13
|
* Cleanup `ImmediateLocation` determinationLukas Wirth2021-05-275-115/+132
|
* Don't complete non-macro item paths in impls and modulesLukas Wirth2021-05-276-29/+76
|
* simplifyLukas Wirth2021-05-277-36/+37
|
* simplifyLukas Wirth2021-05-272-18/+10
|
* Collapse more CompletionContext booleans into enumsLukas Wirth2021-05-276-98/+133
|
* Set `record_pat_syntax` more precisely in CompletionContextLukas Wirth2021-05-263-41/+58
|
* Merge #9015bors[bot]2021-05-264-80/+93
|\ | | | | | | | | | | | | | | | | 9015: Merge pattern completion related bools into an enum r=Veykril a=Veykril The two bools can never both be set so this is basically just a tri-state enum. bors r+ Co-authored-by: Lukas Wirth <[email protected]>
| * Merge pattern completion related bools into an enumLukas Wirth2021-05-264-80/+93
| |
* | Merge #9012bors[bot]2021-05-261-21/+29
|\ \ | |/ |/| | | | | | | | | | | 9012: feat: add tab stops for keyword completions r=matklad a=eduardocanellas Add tab stops for all the keywords that I judged fit. I also introduced some line breaks and spaces, following the pattern I saw in the `postfix` module. Co-authored-by: Eduardo Canellas <[email protected]>
| * feat: add tab stops for keyword completionsEduardo Canellas2021-05-261-21/+29
| |
* | simplifyLukas Wirth2021-05-263-67/+39
|/
* fix: remove undesired completions from trait/impl blocksEduardo Canellas2021-05-261-0/+2
|
* fix: don't show pd/ppd completions where it shouldn't beEduardo Canellas2021-05-252-11/+5
|
* internal: rename hypothetical -> speculativeAleksey Kladov2021-05-242-12/+12
| | | | | Lets steal this good naming from Roslyn before I forget about it yet again.
* Get rid of field_type againFlorian Diebold2021-05-231-4/+3
|
* Infer correct expected type in closureFlorian Diebold2021-05-231-1/+8
| | | | Sadly currently only works if the closure body isn't completely missing.
* Infer correct expected type for generic struct fieldsFlorian Diebold2021-05-232-16/+23
|
* Record method call substs and use them in call infoFlorian Diebold2021-05-231-0/+60
|
* Paper over #8931 a bit moreFlorian Diebold2021-05-231-0/+1
| | | | | | | | | The problem was the skipping of binders in `resolve_method_call_as_callable`; this still doesn't use the _correct_ substitution, but at least it doesn't return a type with free variables in it. Fixes #8931.
* Add test for #8931 and better checkingFlorian Diebold2021-05-231-0/+29
|
* Fix compilation of hir and ide cratesFlorian Diebold2021-05-211-1/+1
|
* Replace ImportGranularity::Guess with guessing boolean flagLukas Tobias Wirth2021-05-191-0/+1
|
* MergeBehavior -> ImportGranularityLukas Tobias Wirth2021-05-181-2/+5
|
* simplifyLukas Wirth2021-05-151-12/+10
|
* Merge #8794bors[bot]2021-05-101-1/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8794: Give MergeBehaviour variants better names r=Veykril a=Veykril I never really liked the variant names I gave this enum from the beginning and then I found out about rustfmt's `imports_granularity` config: > imports_granularity > > How imports should be grouped into use statements. Imports will be merged or split to the configured level of granularity. > > Default value: Preserve > Possible values: Preserve, Crate, Module, Item > Stable: No I personally prefer using `crate` over `full` and `module` over last, they seem more descriptive. Keeping these similar between tooling also seems like a good plus point to me. We might even wanna take over the entire enum at some point if we have a `format/cleanup imports` assists in the future which would probably want to also have the `preserve` and `item` options. Co-authored-by: Lukas Wirth <[email protected]>
| * Give MergeBehaviour variants better namesLukas Wirth2021-05-101-1/+1
| |
* | Corrected 2 typos on line 83mixio2021-05-101-1/+1
|/
* Add `=` to pattern recoveryLukas Wirth2021-05-081-1/+22
|
* Small macro fixKirill Bulatov2021-05-061-1/+1
|
* internal: use API stabilized in 1.52Aleksey Kladov2021-05-061-1/+1
|
* SimplifyEdwin Cheng2021-05-061-6/+2
|
* Fix: Do not overwrite comments and attrs in trait impl completionJesse Bakker2021-05-061-8/+65
|
* simplifyLukas Tobias Wirth2021-05-054-38/+35
|
* Add some cov marks for qualified_path completionLukas Tobias Wirth2021-05-041-5/+8
|
* Complete enum variants through type aliasesLukas Tobias Wirth2021-05-041-7/+33
|
* Make CompletionContext expected_type smarterLukas Tobias Wirth2021-05-032-117/+113
|
* Fix feature description inconsistencyBrandon2021-05-011-1/+1
|
* internal: normalize nameAleksey Kladov2021-04-302-3/+3
| | | | All def types in hir are unsubstituted
* Split out merge_imports module from helpers::insert_useLukas Wirth2021-04-241-4/+1
|
* Add cov_marks to insert_use testsLukas Wirth2021-04-202-2/+2
|
* Remove SyntaxRewriter usage in insert_use in favor of tedLukas Wirth2021-04-201-4/+4
|
* Exclude inherent traits from flyimportsKirill Bulatov2021-04-161-0/+23
|
* Do not show flyimports in trait or impl declarationsKirill Bulatov2021-04-151-0/+50
|
* Use CompletionTextEdit::InsertAndReplace if supported by the clientLukas Wirth2021-04-081-1/+1
|
* Fix typomemoryruins2021-04-071-2/+2
|
* Do not import on the fly during fields of record literal syntaxmemoryruins2021-04-061-0/+43
|
* internal: document hypothetical completion problemAleksey Kladov2021-04-051-0/+28
|
* Resolve associated typesLukas Wirth2021-04-011-1/+1
|
* Merge #8267bors[bot]2021-03-312-0/+4
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8267: Adding gifs and screenshots for features in manual r=matklad a=MozarellaMan For #6539 This includes most of gif or screenshot examples of most items in the "Features" header. With the exceptions of: - **On Typing Assists** - couldn't get it to work for a demo, I'm probably missing something? - **Structural search and replace** - looked to be already a visual example of the feature - **Workspace symbol** - wasn't sure how best to show this, all of the examples maybe? Also wasn't sure of the best code example to show it off - **Semantic Syntax Highlighting** - seemed obvious enough to not need a screenshot, but I could easily add this All the gifs/pngs are hosted in this [comment](https://github.com/rust-analyzer/rust-analyzer/issues/6539#issuecomment-809574840). Please let me know if any of them aren't suitable (and why) and I'll improve it! Or if you don't like the theme/font Co-authored-by: Ayomide Bamidele <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-05 00:41:23 +0000