aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_hir_ty
Commit message (Collapse)AuthorAgeFilesLines
...
* Deal better with implicit type parameters and argument listsFlorian Diebold2020-02-074-26/+138
|
* FormattingFlorian Diebold2020-02-079-38/+82
|
* Clean up RPIT a bitFlorian Diebold2020-02-074-41/+13
|
* Fix compilation of other cratesFlorian Diebold2020-02-072-4/+10
|
* Use variables in predicates as wellFlorian Diebold2020-02-075-63/+52
|
* Comment fixes / todosFlorian Diebold2020-02-073-6/+8
|
* Fix APIT some moreFlorian Diebold2020-02-074-101/+115
|
* Fix APITFlorian Diebold2020-02-071-0/+2
|
* Change Ty::Param to contain param IDFlorian Diebold2020-02-0711-127/+136
|
* WIP use params for APITFlorian Diebold2020-02-073-1/+64
|
* Fix assoc type selectionFlorian Diebold2020-02-072-32/+43
|
* Fix another testFlorian Diebold2020-02-072-7/+3
|
* First stab at desugaring bounds for APITFlorian Diebold2020-02-072-6/+33
|
* Fix crashFlorian Diebold2020-02-071-4/+7
|
* Fix enum constructorsFlorian Diebold2020-02-073-11/+9
|
* Fix printing of function typesFlorian Diebold2020-02-077-72/+73
|
* Lower impl trait to variables, move away from using placeholders where they ↵Florian Diebold2020-02-079-188/+220
| | | | don't belong
* wip lower impl trait to type argsFlorian Diebold2020-02-074-4/+6
|
* wip implement lowering modeFlorian Diebold2020-02-072-26/+34
|
* Add impl trait lowering modeFlorian Diebold2020-02-074-32/+132
|
* Introduce TyLoweringContextFlorian Diebold2020-02-074-146/+130
|
* Standard formatting for array typesAleksey Kladov2020-01-285-89/+89
|
* Tweak Chalk settingsFlorian Diebold2020-01-271-2/+1
|
* Ignore failing impl Trait testsFlorian Diebold2020-01-271-0/+2
|
* Upgrade ChalkFlorian Diebold2020-01-273-61/+71
|
* Update cratesJeremy Kolb2020-01-261-1/+1
|
* Omit default parameters for reference typesKirill Bulatov2020-01-222-2/+7
|
* Fix inference for shift operatorsFlorian Diebold2020-01-173-5/+35
| | | | Fixes #2602.
* Merge #2844bors[bot]2020-01-141-2/+2
|\ | | | | | | | | | | | | | | 2844: Use dummy value for line! and column! macro r=matklad a=edwin0cheng Use dummy value `0` for line! and column! macro. Co-authored-by: Edwin Cheng <[email protected]>
| * Use dummy value for line! and column! macroEdwin Cheng2020-01-141-2/+2
| |
* | Push resolver further upAleksey Kladov2020-01-143-25/+44
| |
* | Push resolver upAleksey Kladov2020-01-141-21/+51
| |
* | Move impls_future to Type, where it belongsAleksey Kladov2020-01-141-2/+1
| |
* | Don't panic if chalk panicsAleksey Kladov2020-01-131-9/+35
|/
* Fix various names, e.g. Iterator not resolving in core preludeFlorian Diebold2020-01-111-0/+54
| | | | | | | | | | | | | Basically, `Iterator` is re-exported via several steps, which happened to not be resolved yet when we got to the prelude import, but since the name resolved to the reexport from `core::iter` (just to no actual items), we gave up trying to resolve it further. Maybe part of the problem is that we can have `PartialResolvedImport::Unresolved` or `PartialResolvedImport::Indeterminate` with `None` in all namespaces, and handle them differently. Fixes #2683.
* Add test for macro expansion in various expressionsFlorian Diebold2020-01-101-0/+81
|
* Expand PAREN_EXPR as expressionEdwin Cheng2020-01-101-0/+17
|
* Merge #2742bors[bot]2020-01-033-4/+13
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2742: Split `infer` query into two for better profiling r=flodiebold a=michalt This is the same change as we did with `crate_def_map` and it does seem that we mostly spend time in salsa, without recomputing much on rust-analyzer side. Example output: ``` 233ms - handle_inlay_hints 163ms - get_inlay_hints 163ms - SourceAnalyzer::new 67ms - def_with_body_from_child_node 67ms - analyze_container 67ms - analyze_container 67ms - Module::from_definition 67ms - Module::from_file 67ms - crate_def_map 0ms - parse_macro_query (6 calls) 0ms - raw_items_query (1 calls) 66ms - ??? 0ms - crate_def_map (1 calls) 0ms - crate_def_map (1 calls) 96ms - infer 2ms - trait_solve_query (2 calls) 94ms - ??? 0ms - body_with_source_map_query (1 calls) 0ms - crate_def_map (1 calls) [...] ``` Signed-off-by: Michal Terepeta <[email protected]> Co-authored-by: Michal Terepeta <[email protected]>
| * Split `infer` query into two for better profilingMichal Terepeta2020-01-033-4/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is the same change as we did with `crate_def_map` and it does seem that we mostly spend time in salsa, without recomputing much on rust-analyzer side. Example output: ``` 233ms - handle_inlay_hints 163ms - get_inlay_hints 163ms - SourceAnalyzer::new 67ms - def_with_body_from_child_node 67ms - analyze_container 67ms - analyze_container 67ms - Module::from_definition 67ms - Module::from_file 67ms - crate_def_map 0ms - parse_macro_query (6 calls) 0ms - raw_items_query (1 calls) 66ms - ??? 0ms - crate_def_map (1 calls) 0ms - crate_def_map (1 calls) 96ms - infer 2ms - trait_solve_query (2 calls) 94ms - ??? 0ms - body_with_source_map_query (1 calls) 0ms - crate_def_map (1 calls) [...] ``` Signed-off-by: Michal Terepeta <[email protected]>
* | Fix #2705Florian Diebold2020-01-032-1/+18
|/ | | | | | | | The `-` turned into a `+` during a refactoring. The original issue was caused by `Read` resolving wrongly to a trait without type parameters instead of a struct with one parameter; this only fixes the crash, not the wrong resolution.
* Resolve traits in infer using lang item infrastructureEmil Lauridsen2019-12-293-10/+19
|
* Don't add non-impl/trait containers to scopeAleksey Kladov2019-12-293-24/+95
|
* Merge #2657bors[bot]2019-12-272-17/+26
|\ | | | | | | | | | | | | | | | | | | 2657: Omit closure parameters in closure type display strings r=flodiebold a=SomeoneToIgnore Part of https://github.com/rust-analyzer/rust-analyzer/issues/1946 I wonder, should we display the the closure trait (Fn/FnMut/FnOnce) in inlay hints instead of `|...|` at all? Co-authored-by: Kirill Bulatov <[email protected]>
| * Omit closure parametersKirill Bulatov2019-12-232-17/+26
| |
* | Merge #2661bors[bot]2019-12-242-2/+78
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | 2661: Implement infer await from async function r=flodiebold a=edwin0cheng This PR is my attempt for trying to add support for infer `.await` expression from an `async` function, by desugaring its return type to `Impl Future<Output=RetType>`. Note that I don't know it is supposed to desugaring it in that phase, if it is not suitable in current design, just feel free to reject it :) r=@flodiebold Co-authored-by: Edwin Cheng <[email protected]>
| * Check if parameters is emptyEdwin Cheng2019-12-241-4/+6
| |
| * Add FIXMEEdwin Cheng2019-12-241-1/+5
| |
| * Implement infer await from async funcEdwin Cheng2019-12-242-2/+72
| |
* | Filter out error predicates in type bounds as wellFlorian Diebold2019-12-222-2/+29
| |
* | Introduce our own Chalk TypeFamily, instead of using ChalkIrFlorian Diebold2019-12-224-87/+126
| | | | | | | | | | | | It's not very different, except we can directly use Salsa IDs instead of casting them. This means we need to refactor the handling of errors to get rid of UNKNOWN_TRAIT though.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-27 13:58:58 +0000