aboutsummaryrefslogtreecommitdiff
path: root/crates/hir_ty/src/infer.rs
Commit message (Collapse)AuthorAgeFilesLines
* clippy::redudant_borrowMaan20032021-06-131-1/+1
|
* Fix coercion in match with expected typeFlorian Diebold2021-06-121-0/+32
| | | | Plus add infrastructure to test type mismatches without expect.
* internal: move missing unsafe diagnostic to hirAleksey Kladov2021-06-121-2/+2
|
* internal: move inference diagnostics to hirAleksey Kladov2021-06-121-53/+9
|
* internal: implement pattern adjustments.Dawer2021-06-011-0/+2
|
* hir_ty: use async ret type for inference inside async bodiescynecx2021-05-291-1/+7
|
* Merge #8973bors[bot]2021-05-251-2/+3
|\ | | | | | | | | | | | | | | 8973: internal: move diagnostics to hir r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * internal: move diagnostics to hirAleksey Kladov2021-05-251-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The idea here is to eventually get rid of `dyn Diagnostic` and `DiagnosticSink` infrastructure altogether, and just have a `enum hir::Diagnostic` instead. The problem with `dyn Diagnostic` is that it is defined in the lowest level of the stack (hir_expand), but is used by the highest level (ide). As a first step, we free hir_expand and hir_def from `dyn Diagnostic` and kick the can up to `hir_ty`, as an intermediate state. The plan is then to move DiagnosticSink similarly to the hir crate, and, as final third step, remove its usage from the ide. One currently unsolved problem is testing. You can notice that the test which checks precise diagnostic ranges, unresolved_import_in_use_tree, was moved to the ide layer. Logically, only IDE should have the infra to render a specific range. At the same time, the range is determined with the data produced in hir_def and hir crates, so this layering is rather unfortunate. Working on hir_def shouldn't require compiling `ide` for testing.
* | Consider trait to be in scope for trait-implLukas Wirth2021-05-251-0/+2
| |
* | Fix type inference not working for new Try traitLukas Wirth2021-05-251-1/+4
|/
* Record method call substs and use them in call infoFlorian Diebold2021-05-231-11/+14
|
* Some remaining cleanupsFlorian Diebold2021-05-211-4/+0
|
* Refactor expectation handlingFlorian Diebold2021-05-211-20/+39
| | | | So as to not use `TyKind::Error` as "no expectation".
* Deal with goals arising from unificationFlorian Diebold2021-05-211-3/+3
|
* Get rid of resolve_ty_as_possibleFlorian Diebold2021-05-211-17/+17
| | | | Instead use shallow resolving where necessary.
* Make resolve_ty_shallow return TyFlorian Diebold2021-05-211-3/+1
|
* Rework obligation handlingFlorian Diebold2021-05-211-69/+15
| | | | | | | | We can't do the easy hack that we did before anymore, where we kept track of whether any inference variables changed since the last time we rechecked obligations. Instead, we store the obligations in canonicalized form; that way we can easily check the inference variables to see whether they have changed since the goal was canonicalized.
* Make diverging type variables work againFlorian Diebold2021-05-211-0/+3
| | | | | Chalk doesn't know about the `diverging` flag, so we need to instead propagate it before fully resolving the variables.
* Temporary fix for unknown expectationsFlorian Diebold2021-05-211-0/+4
|
* Rewrite coercion using the new unificationFlorian Diebold2021-05-211-0/+12
|
* Remove our unification code, use Chalk's insteadFlorian Diebold2021-05-211-11/+7
|
* internal: Record mismatches of pattern types.Dawer2021-05-191-2/+21
|
* Remove unusedFlorian Diebold2021-04-081-1/+0
|
* Replace remaining `fold` callsFlorian Diebold2021-04-081-10/+15
|
* InEnvironment::new takes a referenceFlorian Diebold2021-04-071-1/+1
|
* Merge #8394bors[bot]2021-04-071-33/+37
|\ | | | | | | | | | | | | | | 8394: Infer variants through type aliased enums r=Veykril a=Veykril bors r+ Co-authored-by: Lukas Wirth <[email protected]>
| * Infer variants through type aliased enumsLukas Wirth2021-04-071-33/+37
| |
* | Remove `SolutionVariables`, add ConstrainedSubst analogous to ChalkFlorian Diebold2021-04-061-4/+11
| | | | | | | | ... just missing the constraints.
* | Align `InferenceVar` to ChalkFlorian Diebold2021-04-061-19/+0
| |
* | infer: remove `record_pat_field_resolutions` fieldJonas Schievink2021-04-061-5/+1
|/ | | | | Same as https://github.com/rust-analyzer/rust-analyzer/pull/8376, this can be computed from other data
* infer: remove `record_field_resolutions` fieldJonas Schievink2021-04-061-5/+0
| | | | | It stores no useful data, since we can derive all fields from `variant_resolutions`
* Move Ty accessors to TyExtLukas Wirth2021-04-061-1/+1
|
* Add Interner parameter to Binders::substituteFlorian Diebold2021-04-051-4/+4
|
* Binders::subst -> substituteFlorian Diebold2021-04-051-4/+4
|
* Rename TyKind::Unknown to ErrorLaurențiu Nicola2021-04-051-7/+7
|
* Move things from `traits` module to `types` as wellFlorian Diebold2021-04-041-2/+2
|
* Replace Substitution::bound_vars and ::type_params_for_genericsFlorian Diebold2021-04-041-2/+2
|
* Replace remaining uses of Substitution::build_for_defFlorian Diebold2021-04-041-2/+1
|
* Add and start using TraitRef and ProjectionTy buildersFlorian Diebold2021-04-041-5/+3
|
* Rename Ty::interned to Ty::kindFlorian Diebold2021-04-031-2/+2
| | | | ... since that's the actual method on Chalk side that matches the signature.
* minor: add profile call for resolve_obligationsAleksey Kladov2021-04-021-0/+2
|
* Don't recheck obligations if we have learned nothing newFlorian Diebold2021-04-011-3/+15
| | | | | | | | | | This is just the most trivial check: If no inference variables have been updated, and there are no new obligations, we can just skip trying to solve them again. We could be smarter about it, but this already helps quite a bit, and I don't want to touch this too much before we replace the inference table by Chalk's. Fixes #8263 (well, improves it quite a bit).
* completion relevance consider if types can be unifiedJosh Mcguigan2021-03-261-0/+5
|
* Align InEnvironment with ChalkFlorian Diebold2021-03-211-1/+1
| | | | | | This in particular means storing a chalk_ir::Environment, not our TraitEnvironment. This makes InEnvironment not usable for Type, where we need to keep the full TraitEnvironment.
* Turn Obligation into something similar to chalk_ir::DomainGoalFlorian Diebold2021-03-201-6/+6
| | | | This includes starting to make use of Chalk's `Cast` trait.
* Replace Projection variant in GenericPredicate with AliasEqLukas Wirth2021-03-191-9/+9
|
* Chalkify TraitRefFlorian Diebold2021-03-181-2/+3
|
* Rename Substs -> SubstitutionFlorian Diebold2021-03-161-4/+4
|
* Merge #8018bors[bot]2021-03-151-6/+24
|\ | | | | | | | | | | | | | | | | | | 8018: Make Ty wrap TyKind in an Arc r=flodiebold a=flodiebold ... to further move towards Chalk. This is a bit of a slowdown (218ginstr vs 213ginstr for inference on RA), even though it allows us to unwrap the Substs in `TyKind::Ref` etc.. Co-authored-by: Florian Diebold <[email protected]>
| * Make Ty wrap TyKind in an ArcFlorian Diebold2021-03-141-6/+24
| | | | | | | | | | | | | | | | ... like it will be in Chalk. We still keep `interned_mut` and `into_inner` methods that will probably not exist with Chalk. This worsens performance slightly (5ginstr inference on RA), but doesn't include other simplifications we can do yet.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-04 18:05:16 +0000