aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | Further refactoring under review commentsMikhail Rakhmanov2020-05-241-7/+3
| | | |
| * | | Remove unnecessary set_file and change variable positions for better readabilityMikhail Rakhmanov2020-05-231-2/+1
| | | |
| * | | Remove unwraps where possibleMikhail Rakhmanov2020-05-231-22/+11
| | | |
| * | | Further review fixesMikhail Rakhmanov2020-05-233-14/+12
| | | |
| * | | Use default instead of new in AssistDirectorMikhail Rakhmanov2020-05-231-5/+7
| | | |
| * | | Better naming and fix some review commentsMikhail Rakhmanov2020-05-232-15/+14
| | | |
| * | | More formattingMikhail Rakhmanov2020-05-221-3/+1
| | | |
| * | | Refactor AssistDirectorMikhail Rakhmanov2020-05-221-6/+4
| | | |
| * | | Formatting and remove unused importsMikhail Rakhmanov2020-05-222-16/+21
| | | |
| * | | Add preliminary implementation of extract struct from enum variantMikhail Rakhmanov2020-05-224-1/+402
| | | |
* | | | Merge #4784bors[bot]2020-06-083-40/+20
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4784: Change management of test cfg to better support json projects r=Nashenas88 a=Nashenas88 This helps support json projects where they can decide whether to add the `test` cfg or not. One alternative is to add support for marking json project crates as a sysroot crate, and adding logic to remove the `test` cfg in those cases. In my opinion, that option gives less flexibility to json projects and leads to more functionality that needs to be maintained. Fixes #4508 cc @woody77 Co-authored-by: Paul Daniel Faria <[email protected]> Co-authored-by: Paul Daniel Faria <[email protected]>
| * | | | Use Option<&str> for target instead of Option<&String>Paul Daniel Faria2020-06-082-4/+4
| | | | |
| * | | | Remove default_cfg_options, pass target instead so it can be used for ↵Paul Daniel Faria2020-06-083-38/+19
| | | | | | | | | | | | | | | | | | | | building cargo workspaces
| * | | | Change management of test cfg to better support json projectsPaul Daniel Faria2020-06-073-8/+7
| | | | |
* | | | | Better unsafe highlihgting testsAleksey Kladov2020-06-088-9/+16
| | | | |
* | | | | Highlight only the unsafe operator itselfAleksey Kladov2020-06-081-6/+2
| | | | |
* | | | | Merge #4775bors[bot]2020-06-083-24/+57
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4775: Add goto def for enum variant field r=matklad a=unexge Closes #4764. I'm not familiar with ra codebase, there might be better ways to do that :smile: Co-authored-by: unexge <[email protected]>
| * | | | | Use explicit match for extracting def from `classify_name`unexge2020-06-081-2/+5
| | | | | |
| * | | | | Swap `into_definition` and `definition` semantics for `FieldShorthand` variantunexge2020-06-081-2/+2
| | | | | |
| * | | | | Add `FieldShorthand` variant to `NameClass`unexge2020-06-083-27/+32
| | | | | |
| * | | | | Add goto def for enum variant fieldunexge2020-06-062-0/+25
| |/ / / /
* | | | | Merge #4683bors[bot]2020-06-084-46/+368
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4683: Implement syntax highlighting for doctests r=ltentrup a=ltentrup The implementation is more complicated than the previous injection logic as the doctest comments consist of multiple ranges. The implementation extracts the doctests together with an offset-mapping, applies the syntax highlighting, and updates the text ranges. <img width="478" alt="Bildschirmfoto 2020-06-01 um 15 45 25" src="https://user-images.githubusercontent.com/201808/83415249-1f0b5800-a41f-11ea-8fa6-c282434d6ff7.png"> Part of #4170. Co-authored-by: Leander Tentrup <[email protected]>
| * | | | | Implement syntax highlighting for doctestsLeander Tentrup2020-06-084-46/+368
| | | | | |
* | | | | | Merge #4773bors[bot]2020-06-085-68/+302
|\ \ \ \ \ \ | |/ / / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4773: Run|Debug hover actions. r=matklad a=vsrs ![hover_actions_run](https://user-images.githubusercontent.com/62505555/83335644-dfc1f780-a2b6-11ea-820b-ccaa82290e7d.gif) This hover actions work exactly like corresponding lenses. Co-authored-by: vsrs <[email protected]>
| * | | | | Apply suggestions from code reviewvsrs2020-06-083-21/+21
| | | | | |
| * | | | | Add lib target filtering.vsrs2020-06-061-11/+18
| | | | | |
| * | | | | Disable runnables lookup in macro-generated code.vsrs2020-06-061-1/+10
| | | | | |
| * | | | | Add Run|Debug hover actionsvsrs2020-06-065-24/+174
| | | | | |
| * | | | | Preliminary runnables refactoringvsrs2020-06-063-54/+122
| |/ / / /
* | | | | Merge #4781bors[bot]2020-06-081-32/+27
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4781: Remove redundancy in syntax highlighting tests r=matklad a=ltentrup Follow up from #4683. Improves syntax highlighting testing by introducing a function that contains the boilerplate comparison code. Keeps the `ra_fixture` argument in the first position, thus, the editor syntax highlighting injection still works. Co-authored-by: Leander Tentrup <[email protected]>
| * | | | | Remove redundancy in syntax highlighting testsLeander Tentrup2020-06-071-32/+27
| |/ / / /
* | | | | Merge #4770bors[bot]2020-06-086-104/+33
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4770: Clean up handling of int/float literal types r=matklad a=flodiebold 'Unknown' int/float types actually never exist as such, they get replaced by type variables immediately. So the whole `Uncertain<IntTy>` thing was unnecessary and just led to a bunch of match branches that were never hit. Co-authored-by: Florian Diebold <[email protected]>
| * | | | | Clean up handling of int/float literal typesFlorian Diebold2020-06-066-104/+33
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | 'Unknown' int/float types actually never exist as such, they get replaced by type variables immediately. So the whole `Uncertain<IntTy>` thing was unnecessary and just led to a bunch of match branches that were never hit.
* / / / / Fix bug in lexer for format specifier where the `type` and `width` were not ↵Leander Tentrup2020-06-072-15/+24
|/ / / / | | | | | | | | | | | | correctly distinguished
* | | | Fix type parameter defaultsFlorian Diebold2020-06-0510-115/+192
| | | | | | | | | | | | | | | | | | | | They should not be applied in expression or pattern contexts, unless there are other explicitly given type args.
* | | | Merge #4761bors[bot]2020-06-052-2/+7
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4761: Upgrade Chalk to published version r=matklad a=flodiebold CC @pksunkara Co-authored-by: Florian Diebold <[email protected]>
| * | | | Upgrade Chalk to published versionFlorian Diebold2020-06-052-2/+7
| | | | |
* | | | | Merge #4689bors[bot]2020-06-0512-81/+442
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4689: Implement return position impl trait / opaque type support r=matklad a=flodiebold This is working, but I'm not that happy with how the lowering works. We might need an additional representation between `TypeRef` and `Ty` where names are resolved and `impl Trait` bounds are separated out, but things like inference variables don't exist and `impl Trait` is always represented the same way. Also note that this doesn't implement correct handling of RPIT *inside* the function (which involves turning the `impl Trait`s into variables and creating obligations for them). That intermediate representation might help there as well. Co-authored-by: Florian Diebold <[email protected]> Co-authored-by: Florian Diebold <[email protected]>
| * | | | | Review fixesFlorian Diebold2020-06-055-25/+68
| | | | | |
| * | | | | Implement return position impl trait / opaque type supportFlorian Diebold2020-06-0510-77/+395
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is working, but I'm not that happy with how the lowering works. We might need an additional representation between `TypeRef` and `Ty` where names are resolved and `impl Trait` bounds are separated out, but things like inference variables don't exist and `impl Trait` is always represented the same way. Also note that this doesn't implement correct handling of RPIT *inside* the function (which involves turning the `impl Trait`s into variables and creating obligations for them). That intermediate representation might help there as well.
* | | | | Merge #4760bors[bot]2020-06-056-79/+35
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4760: Minimize FileLoader interface r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | | Minimize FileLoader interfaceAleksey Kladov2020-06-056-79/+35
| |/ / / /
| | | | |
| \ \ \ \
*-. \ \ \ \ Merge #4729 #4748bors[bot]2020-06-0517-162/+795
|\ \ \ \ \ \ | |_|/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4729: Hover actions r=matklad a=vsrs This PR adds a `hoverActions` LSP extension and a `Go to Implementations` action as an example: ![hover_actions_impl](https://user-images.githubusercontent.com/62505555/83335732-6d9de280-a2b7-11ea-8cc3-75253d062fe0.gif) 4748: Add an `ImportMap` and use it to resolve item paths in `find_path` r=matklad a=jonas-schievink Removes the "go faster" queries I added in https://github.com/rust-analyzer/rust-analyzer/pull/4501 and https://github.com/rust-analyzer/rust-analyzer/pull/4506. I've checked this PR on the rustc code base and the assists are still fast. This should fix https://github.com/rust-analyzer/rust-analyzer/issues/4515. Note that this does introduce a change in behavior: We now always refer to items defined in external crates using paths through the external crate. Previously we could also use a local path (if for example the extern crate was reexported locally), as seen in the changed test. If that is undesired I can fix that, but the test didn't say why the previous behavior would be preferable. Co-authored-by: vsrs <[email protected]> Co-authored-by: Jonas Schievink <[email protected]> Co-authored-by: Jonas Schievink <[email protected]>
| | * | | | Clarify when we visit modules multiple timesJonas Schievink2020-06-051-1/+3
| | | | | |
| | * | | | impl Debug for ImportMapJonas Schievink2020-06-051-19/+23
| | | | | |
| | * | | | Reorder importsJonas Schievink2020-06-053-5/+7
| | | | | |
| | * | | | Make `find_path_inner` private againJonas Schievink2020-06-051-1/+1
| | | | | |
| | * | | | Measure memory usage of ImportMapJonas Schievink2020-06-052-5/+6
| | | | | |
| | * | | | defining_crate -> krateJonas Schievink2020-06-052-2/+3
| | | | | |
| | * | | | Fix wrong commentJonas Schievink2020-06-051-1/+1
| | | | | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-14 15:03:01 +0000