aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* | | add links to readmeAleksey Kladov2019-03-261-0/+6
| | |
* | | Merge #1057bors[bot]2019-03-268-125/+131
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1057: simplify r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | simplifyAleksey Kladov2019-03-263-8/+6
| | | |
| * | | move source_id to a separate fileAleksey Kladov2019-03-268-120/+128
|/ / /
* | | Merge #1055bors[bot]2019-03-268-144/+105
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1055: store macro def inside macro id r=matklad a=matklad This makes macro expansion resilient to changes to code inside the macro Co-authored-by: Aleksey Kladov <[email protected]>
| * | | make macro parsing a queryAleksey Kladov2019-03-263-5/+8
| | | |
| * | | reduce visibilityAleksey Kladov2019-03-261-23/+27
| | | |
| * | | store macro def inside macro idAleksey Kladov2019-03-267-119/+73
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This solves the problem of "macro expansion can't call into name resolution, because name resolution calls back into macro expansion" Because we store macro def as a part of call id, macro expansion just knows the def!
* | | | Merge #1056bors[bot]2019-03-261-4/+4
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | 1056: :arrow_up: vfs r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | :arrow_up: vfsAleksey Kladov2019-03-261-4/+4
|/ / /
* | | Merge #1040bors[bot]2019-03-2512-34/+208
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1040: Trait beginnings r=matklad a=flodiebold This adds some very simple trait method resolution, going through traits in scope, looking for methods of the given name, and checking very naively whether there's an impl for the given type and trait. Co-authored-by: Florian Diebold <[email protected]>
| * | | Clean up comments / use nicer Iterator methodsFlorian Diebold2019-03-252-10/+15
| | | |
| * | | Implement a very naive implements checkFlorian Diebold2019-03-254-12/+50
| | | | | | | | | | | | | | | | ... to make the infer_trait_method_simple test have the correct result.
| * | | Basics for trait method resolutionFlorian Diebold2019-03-2511-25/+156
|/ / /
* | | Merge #1049bors[bot]2019-03-251-2/+17
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 1049: Add description & example for inlining local variable r=matklad a=gfreezy Co-authored-by: gfreezy <[email protected]>
| * | markdown syntaxgfreezy2019-03-251-2/+2
| | |
| * | add desc and examples for inline variable actiongfreezy2019-03-251-0/+15
|/ /
| * Assist to flip (some) binary expressions.Marco Groppo2019-03-253-88/+151
|/ | | | This assist can flip the following operators: ==, !=, >, >=, <, <=.
* Merge #1037bors[bot]2019-03-252-0/+300
|\ | | | | | | | | | | | | | | 1037: inline immutable local varialbe r=matklad a=gfreezy resolved #1033 Co-authored-by: gfreezy <[email protected]>
| * use | instead of multiple match armsgfreezy2019-03-251-27/+27
| |
| * inline immutable local varialbegfreezy2019-03-252-0/+300
| |
* | Merge #1034bors[bot]2019-03-2515-165/+424
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1034: HIR diagnostics API r=matklad a=matklad This PR introduces diagnostics API for HIR, so we can now start issuing errors and warnings! Here are requirements that this solution aims to fulfill: * structured diagnostics: rather than immediately rendering error to string, we provide a well-typed blob of data with error-description. These data is used by IDE to provide fixes * open set diagnostics: there's no single enum with all possible diagnostics, which hopefully should result in better modularity The `Diagnostic` trait describes "a diagnostic", which can be downcast to a specific diagnostic kind. Diagnostics are expressed in terms of macro-expanded syntax tree: they store pointers to syntax nodes. Diagnostics are self-contained: you don't need any context, besides `db`, to fully understand the meaning of a diagnostic. Because diagnostics are tied to the source, we can't store them in salsa. So subsystems like type-checking produce subsystem-local diagnostic (which is a closed `enum`), which is expressed in therms of subsystem IR. A separate step converts these proto-diagnostics into `Diagnostic`, by merging them with source-maps. Note that this PR stresses type-system quite a bit: we now type-check every function in open files to compute errors! Discussion on Zulip: https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0/topic/Diagnostics.20API Co-authored-by: Aleksey Kladov <[email protected]>
| * | move tests to where they belongAleksey Kladov2019-03-254-44/+32
| | |
| * | simplifyAleksey Kladov2019-03-251-6/+1
| | |
| * | tweak diagnostics APIAleksey Kladov2019-03-253-11/+16
| | |
| * | test diagnosticsAleksey Kladov2019-03-253-1/+61
| | |
| * | more enterprisey diagnostics setupAleksey Kladov2019-03-253-59/+75
| | |
| * | fixesAleksey Kladov2019-03-252-4/+3
| | |
| * | check impls as wellAleksey Kladov2019-03-252-1/+10
| | |
| * | cleanupAleksey Kladov2019-03-256-51/+70
| | |
| * | switch modules to new diagnosticsAleksey Kladov2019-03-258-135/+156
| | |
| * | allow dyn diagnosticsAleksey Kladov2019-03-256-33/+112
| | |
| * | diagnosticsAleksey Kladov2019-03-256-6/+74
| | |
* | | Merge #1047bors[bot]2019-03-251-39/+36
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1047: :arrow_up: deps r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | :arrow_up: depsAleksey Kladov2019-03-251-39/+36
|/ / /
* | | Merge #1019bors[bot]2019-03-2510-79/+7
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1019: structure moved to ra_ide_api r=matklad a=pasa structure subtask for #1009 Co-authored-by: Sergey Parilin <[email protected]>
| * | | structure moved to ra_ide_apiSergey Parilin2019-03-2510-79/+7
|/ / / | | | | | | | | | ra_ide_api_light removed completely
* | | Merge #1045bors[bot]2019-03-251-37/+34
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1045: simplify r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | simplifyAleksey Kladov2019-03-251-37/+34
|/ / /
* | | Merge #1044bors[bot]2019-03-251-1/+1
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 1044: fix build r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | fix buildAleksey Kladov2019-03-251-1/+1
| | |
* | | Merge #1041bors[bot]2019-03-255-63/+105
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 1041: Add convenience functions to SourceChange for creating single edits r=matklad a=vipentti Fixes #1018 Co-authored-by: Ville Penttinen <[email protected]>
| * | Rename source_edit to source_file_edit to match file_system_editVille Penttinen2019-03-255-11/+11
| | |
| * | Further improvements to the SourceChange convenience methodsVille Penttinen2019-03-254-27/+50
| | | | | | | | | | | | | | | Rename system_edit to file_system_edit, add more documentation, add source_file_edit_from to create a SourceChange from `FileId` and `TextEdit`.
| * | Add convenience functions to SourceChange for creating single editsVille Penttinen2019-03-244-44/+63
| | |
* | | Merge #1043bors[bot]2019-03-252-2/+5
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1043: link docs from dev docs, not from the main readme r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | link docs from dev docs, not from the main readmeAleksey Kladov2019-03-252-2/+5
| | | | | | | | | | | | | | | | If you want to **use** ra, you don't need api docs
* | | | Merge #1042bors[bot]2019-03-251-27/+20
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1042: Remove windows from CI r=matklad a=matklad We don't actually look at the CI results for windows anyway! In general, rust-analyzer should be written in a completely OS-independent way. That is, testing on one OS should be enough. If this is not the case, that means something is seriously broken. No doubt there are components which actually talk to the outside world, and they may be platform dependent. We should extract such components to a separate repo with an extensive multi platform CI, like we did for VFS Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | Remove windows from CIAleksey Kladov2019-03-251-27/+20
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We don't actually look at the CI results for windows anyway! In general, rust-analyzer should be written in a completely OS-independent way. That is, testing on one OS should be enough. If this is not the case, that means something is seriously broken. No doubt there are components which actually talk to the outside world, and they may be platform dependent. We should extract such components to a separate repo with an extensive multi platform CI, like we did for VFS
* | | | Merge #1036bors[bot]2019-03-254-35/+135
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1036: Assist to flip equality (==) and negated equality (!=) operands. r=matklad a=marcogroppo This PR adds an assist to flip the equality operands. I hope this is the right way to do this (I'm a newbie...) Fixes #1023. Co-authored-by: Marco Groppo <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-02 14:35:36 +0000