aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
* Merge #3707bors[bot]2020-03-255-59/+50
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3707: Add ItemScope::visibility_of r=matklad a=edwin0cheng ~This PR implements `HasVisibility` for various constructs and change `Definition::search_scope` to use `Visibility` directly instead of depends on ad-hoc string parsing.~ This PR added `visibility_of` in `ItemScope` and `Module` and use it directly directly instead of depends on ad-hoc string parsing. And also add a FIXME to indicate that there is a bug which do not search child-submodules in other files recursively in `Definition::search_scope`. I will submit another PR to fix that bug after this is merged. cc @flodiebold Co-authored-by: Edwin Cheng <[email protected]>
| * Use visibility_of in searchEdwin Cheng2020-03-241-35/+31
| |
| * Add ItemScope::visibility_ofEdwin Cheng2020-03-244-24/+19
| |
* | Improvements based on code review feedbackMatt Hooper2020-03-241-5/+5
| |
* | Fmt correctionsMatt Hooper2020-03-241-13/+9
| |
* | Added more unit testsMatt Hooper2020-03-241-76/+159
| |
* | Added new inlay hint kind and rules for method chainingMatt Hooper2020-03-245-5/+98
| |
* | Merge #3664bors[bot]2020-03-242-171/+250
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | 3664: Introduce TokenConverter Trait r=matklad a=edwin0cheng This PR add a `TokenConverter` Trait to share the conversion logic between raw `lexer` token and Syntax Node Token. Related #2158. Co-authored-by: Edwin Cheng <[email protected]>
| * | Add open delim when delim not matchEdwin Cheng2020-03-202-5/+28
| | |
| * | Fix text range bug and reorderEdwin Cheng2020-03-201-14/+19
| | |
| * | Add TokenConvertor traitEdwin Cheng2020-03-202-239/+155
| | |
| * | Add test for delim bugEdwin Cheng2020-03-202-12/+147
| | |
* | | Merge #3708bors[bot]2020-03-247-121/+270
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | 3708: Generalise syntax rewriting infrastructure to allow removal of nodes r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | Generalise syntax rewriting infrastructure to allow removal of nodesAleksey Kladov2020-03-247-121/+252
| | |
| * | Add a testAleksey Kladov2020-03-231-0/+18
| | |
* | | Merge #3705bors[bot]2020-03-243-5/+5
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3705: Align naming r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | Align namingAleksey Kladov2020-03-243-5/+5
| | | |
* | | | Merge #3700bors[bot]2020-03-243-47/+50
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3700: fill match arms with empty block rather than unit tuple r=matklad a=JoshMcguigan As requested by @Veetaha in #3689 and #3687, this modifies the fill match arms assist to create match arms as an empty block `{}` rather than a unit tuple `()`. In one test I left one of the pre-existing match arms as a unit tuple, and added a body to another match arm, to demonstrate that the contents of existing match arms persist. Co-authored-by: Josh Mcguigan <[email protected]>
| * | | fill match arms with empty block rather than unit tupleJosh Mcguigan2020-03-243-47/+50
| | | |
* | | | Merge #3694bors[bot]2020-03-241-1/+61
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3694: Complete only missing fields r=matklad a=SomeoneToIgnore Co-authored-by: Kirill Bulatov <[email protected]>
| * | | | Code review fixesKirill Bulatov2020-03-241-3/+4
| | | | | | | | | | | | | | | | | | | | Co-Authored-By: Aleksey Kladov <[email protected]>
| * | | | Complete only missing fieldsKirill Bulatov2020-03-231-1/+60
| | | | |
| | | | |
| \ \ \ \
| \ \ \ \
| \ \ \ \
*---. \ \ \ \ Merge #3696 #3698 #3703bors[bot]2020-03-241-17/+123
|\ \ \ \ \ \ \ | | |_|/ / / / | |/| | / / / | | | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3696: vscode: more type safety r=matklad a=Veetaha 3698: Consider references when applying postfix completions r=matklad a=SomeoneToIgnore Sometimes my RA debugging workflow breaks because `.dbg` is applied to the variable that is used later in the code. It's safer to consider the refences to avoid this for completions that may trigger the move. 3703: Don't try to enable proposed API's on stable r=matklad a=matklad bors r+ 🤖 Co-authored-by: veetaha <[email protected]> Co-authored-by: Kirill Bulatov <[email protected]> Co-authored-by: Aleksey Kladov <[email protected]>
| | * / / / Consider references when applying postfix completionsKirill Bulatov2020-03-231-17/+123
| | |/ / /
* | | | | Add a testKirill Bulatov2020-03-242-9/+45
| | | | |
* | | | | Use more generic public apiKirill Bulatov2020-03-248-47/+56
| | | | |
* | | | | Remove the upcastKirill Bulatov2020-03-241-3/+7
| | | | |
* | | | | Auto import macrosKirill Bulatov2020-03-245-34/+46
| |/ / / |/| | |
* | | | update itertools version to 0.9.0Josh Mcguigan2020-03-236-6/+6
|/ / /
* | | Merge #3689bors[bot]2020-03-233-14/+256
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3689: implement fill match arm assist for tuple of enums r=matklad a=JoshMcguigan This updates the fill match arm assist to work in cases where the user is matching on a tuple of enums. Note, for now this does not apply when some match arms exist (other than the trivial `_`), but I think this could be added in the future. I think this also lays the groundwork for filling match arms when matching on tuples of non-enum values, for example a tuple of an enum and a boolean. Co-authored-by: Josh Mcguigan <[email protected]>
| * | review commentsJosh Mcguigan2020-03-232-17/+114
| | |
| * | implement fill match arm assist for tuple of enumsJosh Mcguigan2020-03-233-14/+159
| | |
* | | Merge pull request #3686 from Veetaha/feature/hover-actual-type-paramsAleksey Kladov2020-03-232-15/+17
|\ \ \ | | | | | | | | ra_hir: add more privacy for Type
| * | | ra_hir: add more privacy for Typeveetaha2020-03-232-15/+17
| | | |
* | | | Merge pull request #3678 from edwin0cheng/refactor-renameAleksey Kladov2020-03-234-26/+112
|\ \ \ \ | | | | | | | | | | Fix rename argument in macro call
| * | | | Fix typoEdwin Cheng2020-03-221-1/+1
| | | | | | | | | | | | | | | Co-Authored-By: Veetaha <[email protected]>
| * | | | Add testEdwin Cheng2020-03-221-0/+57
| | | | |
| * | | | Improve find_all_ref work inside macroEdwin Cheng2020-03-221-9/+23
| | | | |
| * | | | Refactor searchEdwin Cheng2020-03-221-16/+4
| | | | |
| * | | | Add find_node_at_offset_with_descendEdwin Cheng2020-03-221-1/+28
| | | | |
* | | | | Merge #3690bors[bot]2020-03-231-0/+12
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3690: ra_hir: add more docs r=matklad a=Veetaha Cited from [hear](https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0/topic/hover/near/191446937) Co-authored-by: veetaha <[email protected]>
| * | | | | ra_hir: fix typoveetaha2020-03-231-1/+1
| | | | | |
| * | | | | ra_hir: add more docsveetaha2020-03-231-0/+12
| | |_|/ / | |/| | |
* | | | | Merge #3632bors[bot]2020-03-232-35/+59
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3632: ra_cargo_watch: log errors r=matklad a=Veetaha Until this moment we totally ignored all the errors from cargo process. Though this is still true, but we now try to log ones that are critical (i.e. misconfiguration errors and ignore compile errors). This fixes #3631, and gives us a better error message to more gracefully handle the #3265 ![image](https://user-images.githubusercontent.com/36276403/76958683-d7e1f080-6920-11ea-83d8-04561c11ccc4.png) Though I think that outputting this only to `Output` channel is not enough. We should somehow warn the user that he passed wrong arguments to `cargo-watch.args`. I didn't bother looking for how to do this now, but this PR at least gives us something. *cc* @kiljacken @matklad Co-authored-by: veetaha <[email protected]> Co-authored-by: Veetaha <[email protected]>
| * | | | | ra_cargo_watch: log exit code tooveetaha2020-03-221-1/+5
| | | | | |
| * | | | | Smol self-nitVeetaha2020-03-211-1/+1
| | | | | |
| * | | | | fix: typoveetaha2020-03-211-1/+1
| | | | | |
| * | | | | ra_cargo_watch: return Result<> from run_cargo(), and don't read stderr for nowveetaha2020-03-212-49/+56
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As stated by matklad, reading the stderr should be done alngside with stdout via select() (or I guess poll()), there is no such implementation in stdlib, since it is quite low level and platform-dependent and it also requires quite a bit of unrelated code we don't use it for now. As referenced by bjorn3, there is an implementation of the needed read2() function in rustc compiletest. The better solution will be to extract this function to a separate crate in future: https://github.com/rust-analyzer/rust-analyzer/pull/3632#discussion_r395605298
| * | | | | ra_cargo_watch: log more errorsveetaha2020-03-211-3/+16
| | | | | |
* | | | | | Merge #3681bors[bot]2020-03-232-40/+26
|\ \ \ \ \ \ | |_|/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3681: Only include machine-applicable suggestions r=kiljacken a=lnicola Fixes #3676 Fixes #3633 Fixes #3391 r? @kiljacken Co-authored-by: LaurenÈ›iu Nicola <[email protected]>