aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_analysis
Commit message (Collapse)AuthorAgeFilesLines
* Use From to get an owned ASTAleksey Kladov2018-11-011-2/+1
|
* remove SyntaxPtrDatabaseAleksey Kladov2018-11-014-19/+12
|
* Fix testAleksey Kladov2018-10-311-0/+1
|
* Speedup fmtAleksey Kladov2018-10-311-6/+1
|
* RemoveDeadCodeAleksey Kladov2018-10-311-17/+0
|
* Reformat allAleksey Kladov2018-10-3116-230/+278
|
* Simplify find_all_refs by always resolving a ast::BindPatJeremy A. Kolb2018-10-311-32/+16
|
* Add DeclarationDescriptor and ReferenceDescriptorJeremy A. Kolb2018-10-313-4/+77
| | | | | Fixes #142 Fixes #146
* Merge #167bors[bot]2018-10-312-3/+204
|\ | | | | | | | | | | | | | | | | | | | | | | 167: Attempt to extract useful comments from function signatures r=matklad a=kjeremy I'm trying to extract useful function comments for signature info. This will also be useful for hover. This is a WIP (and actually works pretty well!) but I don't think it's the right approach long term so some guidance would be appreciated so that we could also get comments for say types and variable instances etc. Currently `test_fn_signature_with_simple_doc` fails due to a bug in `extend` but we probably shouldn't use this approach anyway. Maybe comments should be attached to nodes somehow? I'm also thinking that maybe the markdown bits should live in the language server. Thoughts? Co-authored-by: Jeremy A. Kolb <[email protected]>
| * Useful comments from function signaturesJeremy A. Kolb2018-10-312-3/+204
| |
* | Add MockAnalysis to make testing easierAleksey Kladov2018-10-316-71/+146
| |
* | Prevent panic by initializing LibrariesQueryJeremy A. Kolb2018-10-311-0/+2
|/
* Merge #177bors[bot]2018-10-313-3/+3
|\ | | | | | | | | | | | | | | 177: Librariese -> Libraries r=matklad a=kjeremy Co-authored-by: Jeremy A. Kolb <[email protected]>
| * Fix typoJeremy A. Kolb2018-10-313-3/+3
| |
* | Merge #176bors[bot]2018-10-3114-161/+1340
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | 176: Move completio to ra_analysis r=matklad a=matklad While we should handle completion for isolated file, it's better achieved by using empty Analysis, rather than working only with &File: we need memoization for type inference even inside a single file. Co-authored-by: Aleksey Kladov <[email protected]>
| * | Move completion to ra_analysisAleksey Kladov2018-10-316-63/+711
| | | | | | | | | | | | | | | | | | While we should handle completion for isolated file, it's better achieved by using empty Analysis, rather than working only with &File: we need memoization for type inference even inside a single file.
| * | move resolve local nameAleksey Kladov2018-10-314-11/+29
| | |
| * | Move FnDescriptors to analyzerAleksey Kladov2018-10-3112-97/+610
| |/
* / Fix typosJeremy A. Kolb2018-10-311-2/+2
|/
* Merge #171bors[bot]2018-10-306-22/+215
|\ | | | | | | | | | | | | | | 171: Query-based module scopes r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * Add ModuleScope as a queryAleksey Kladov2018-10-306-22/+215
| | | | | | | | | | | | | | This is a first step towards queryifing completion and resolve. Some code currently duplicates ra_editor: the plan is to move all completion from ra_editor, but it'll take more than one commit.
* | :arrow_up: salsaAleksey Kladov2018-10-303-5/+10
|/
* Merge #168bors[bot]2018-10-301-1/+1
|\ | | | | | | | | | | | | | | 168: Fix param number r=matklad a=kjeremy Fixes the parameter number if we are not in a method Co-authored-by: Jeremy A. Kolb <[email protected]>
| * Fix param numberJeremy A. Kolb2018-10-301-1/+1
| |
* | switch to TextRange::subrangeAleksey Kladov2018-10-301-2/+1
| |
* | introduce syntax-ptrAleksey Kladov2018-10-302-0/+68
|/
* gc syntax treesAleksey Kladov2018-10-291-2/+3
|
* Index files in parallelAleksey Kladov2018-10-291-9/+13
|
* restore symbols filteringAleksey Kladov2018-10-251-5/+8
|
* Move input to top-levelAleksey Kladov2018-10-258-59/+64
|
* Remove unneded HashAleksey Kladov2018-10-251-14/+1
|
* dead codeAleksey Kladov2018-10-251-116/+0
|
* dead codeAleksey Kladov2018-10-251-22/+0
|
* Encapsulate CrateGraph a bitAleksey Kladov2018-10-253-12/+21
|
* re-enable cancelationAleksey Kladov2018-10-252-9/+7
|
* use correct file when resolving callablesAleksey Kladov2018-10-251-2/+3
|
* disable cancelationAleksey Kladov2018-10-251-6/+8
|
* Improve loggingAleksey Kladov2018-10-254-11/+20
|
* Store all the data in the Salsa DatabaseAleksey Kladov2018-10-259-172/+281
|
* Complete crate:: pathsAleksey Kladov2018-10-245-6/+98
|
* simplify rootsAleksey Kladov2018-10-244-38/+18
|
* SimplifyAleksey Kladov2018-10-241-3/+3
|
* make indexing parallel againAleksey Kladov2018-10-242-4/+5
|
* revive the testAleksey Kladov2018-10-241-6/+6
|
* Merge #157bors[bot]2018-10-2310-443/+493
|\ | | | | | | | | | | | | | | | | | | | | 157: Introduce ModuleId r=matklad a=matklad Previously, module was synonym with a file, and so a module could have had several parents. This commit introduces a separate module concept, such that each module has only one parent, but a single file can correspond to different modules. Co-authored-by: Aleksey Kladov <[email protected]>
| * Introduce ModuleIdAleksey Kladov2018-10-2310-443/+493
| | | | | | | | | | | | | | Previously, module was synonym with a file, and so a module could have had several parents. This commit introduces a separate module concept, such that each module has only one parent, but a single file can correspond to different modules.
* | Cargo Update runJeremy A. Kolb2018-10-231-1/+1
|/ | | | | | | Bump relative-path to 0.4.0 Failure 0.1.3 to fix leak with downcast Updated everything else too
* Merge #138bors[bot]2018-10-223-6/+11
|\ | | | | | | | | | | | | | | | | | | | | | | 138: Fix some clippy lints r=matklad a=alanhdu I went ahead and fixed all the clippy lints (there were a couple I thought would be better unfixed and added `cfg` statements to allow them) and also re-enabled clippy and rustfmt in CI. They were disabled with `no time to explain, disable clippy checks`, so hopefully this won't go against whatever the reason at the time was :laughing:. One question about the CI though: right now, it's an allowed failure that runs against the latest nightly each time. Would it be better to pin it to a specific nightly (or use the `beta` versions) to lower the churn? Co-authored-by: Alan Du <[email protected]>
| * Revert "clippy: Fix new_ret_no_self"Alan Du2018-10-204-5/+5
| | | | | | | | This reverts commit 2ae9dfa812ccf18867373f77a106161378a6d91d.
| * Fix function callsAlan Du2018-10-182-3/+2
| |