aboutsummaryrefslogtreecommitdiff
path: root/crates/hir_ty/src/infer
Commit message (Collapse)AuthorAgeFilesLines
* Merge #9260bors[bot]2021-06-141-3/+3
|\ | | | | | | | | | | | | | | 9260: tree-wide: make rustdoc links spiky so they are clickable r=matklad a=lf- Rustdoc was complaining about these while I was running with --document-private-items and I figure they should be fixed. Co-authored-by: Jade <[email protected]>
| * tree-wide: make rustdoc links spiky so they are clickableJade2021-06-141-3/+3
| |
* | cargo fmtMaan20032021-06-131-7/+1
| |
* | clippy::redundant_field_namesMaan20032021-06-131-1/+1
| |
* | clippy::redudant_borrowMaan20032021-06-134-11/+11
| |
* | Fix coercion in match with expected typeFlorian Diebold2021-06-121-1/+6
|/ | | | Plus add infrastructure to test type mismatches without expect.
* Merge #9105bors[bot]2021-06-031-0/+7
|\ | | | | | | | | | | | | | | | | | | | | 9105: internal: calculate pattern adjustments r=flodiebold a=iDawer This extends `InferenceResult` with `pub pat_adjustments: FxHashMap<PatId, Vec<Ty>>`. Fixes #9095 Co-authored-by: Dawer <[email protected]>
| * internal: implement pattern adjustments.Dawer2021-06-011-0/+7
| |
* | Fix bind patterns always being treated as ref taking patternsLukas Wirth2021-06-021-0/+4
|/
* hir_ty: use correct receiver_ty in method resolutioncynecx2021-05-311-11/+2
|
* Update salsaJonas Schievink2021-05-271-1/+1
|
* Merge #9007bors[bot]2021-05-263-17/+15
|\ | | | | | | | | | | | | | | 9007: Internal: `clippy::redundant_clone` fixes r=lnicola a=lnicola bors r+ Co-authored-by: Laurențiu Nicola <[email protected]>
| * clippy::redundant_clone fixesLaurențiu Nicola2021-05-263-17/+15
| |
* | Fix type mismatch caused by macrosFlorian Diebold2021-05-251-1/+1
|/ | | | | | MacroStmts should be completely transparent, but it prevented coercion. (I should maybe give `infer_expr` and `infer_expr_inner` better names.)
* Record method call substs and use them in call infoFlorian Diebold2021-05-232-18/+23
|
* Resolve any lifetime variables to 'static after inferenceFlorian Diebold2021-05-221-1/+13
| | | | | | | | Chalk's unification can sometimes create lifetime variables, which we currently don't really deal with, but at least we don't want to leak them outside of inference. Should fix #8919.
* Clean up visibilitiesFlorian Diebold2021-05-211-10/+10
|
* Some remaining cleanupsFlorian Diebold2021-05-212-14/+13
|
* Record type mismatches for failed coercions in match etc.Florian Diebold2021-05-212-15/+21
|
* Refactor expectation handlingFlorian Diebold2021-05-212-34/+49
| | | | So as to not use `TyKind::Error` as "no expectation".
* Remove TypeVariableTableFlorian Diebold2021-05-212-56/+48
|
* Deal with goals arising from unificationFlorian Diebold2021-05-212-14/+17
|
* Get rid of resolve_ty_as_possibleFlorian Diebold2021-05-215-62/+30
| | | | Instead use shallow resolving where necessary.
* Make resolve_ty_shallow return TyFlorian Diebold2021-05-212-11/+6
|
* Rework obligation handlingFlorian Diebold2021-05-214-31/+157
| | | | | | | | 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.
* Fix another panicFlorian Diebold2021-05-211-17/+15
|
* Fix panicFlorian Diebold2021-05-211-1/+4
|
* Fix HIR expecting errors to unify with anythingFlorian Diebold2021-05-211-2/+6
|
* Fix if/else coercionFlorian Diebold2021-05-211-1/+4
|
* Make diverging type variables work againFlorian Diebold2021-05-211-0/+20
| | | | | Chalk doesn't know about the `diverging` flag, so we need to instead propagate it before fully resolving the variables.
* Fix handling of diverging branches in match coercionFlorian Diebold2021-05-211-4/+13
| | | | Fixes #7626.
* Fix coercion of two closures to a function pointerFlorian Diebold2021-05-211-19/+31
| | | | Fixes #8604.
* Update tests with expected changesFlorian Diebold2021-05-211-3/+0
|
* Make type resolver a proper folder, make it resolve consts as wellFlorian Diebold2021-05-211-48/+117
|
* Fix fallback to bound vars in `unify`Florian Diebold2021-05-211-45/+78
|
* Temporary fix for unknown expectationsFlorian Diebold2021-05-211-0/+4
|
* Fix warnings & formatFlorian Diebold2021-05-212-17/+8
|
* Rewrite coercion using the new unificationFlorian Diebold2021-05-212-96/+342
|
* Remove our unification code, use Chalk's insteadFlorian Diebold2021-05-214-414/+109
|
* internal: Record mismatches of pattern types.Dawer2021-05-192-6/+10
|
* Merge #8813bors[bot]2021-05-161-20/+12
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8813: Get some more array lengths! r=lf- a=lf- This is built on #8799 and thus contains its changes. I'll rebase it onto master when that one gets merged. It adds support for r-a understanding the length of: * `let a: [u8; 2] = ...` * `let a = b"aaa"` * `let a = [0u8; 4]` I have added support for getting the values of byte strings, which was not previously there. I am least confident in the correctness of this part and it probably needs some more tests, as we currently have only one test that exercised that part (!). Fixes #2922. Co-authored-by: Jade <[email protected]>
| * Address final feedbackJade2021-05-161-3/+2
| | | | | | | | | | * rename ConstExtension->ConstExt * refactor a manual construction of a Const
| * Add more tests, refactor array lengths/consteval workJade2021-05-141-33/+8
| | | | | | | | | | | | | | | | | | | | | | Fix #2922: add unknown length as a condition for a type having unknown. Incorporate reviews: * Extract some of the const evaluation workings into functions * Add fixmes on the hacks * Add tests for impls on specific array lengths (these work!!! 😁) * Add tests for const generics (indeed we don't support it yet)
| * Add support for lengths in array repeats, if they are literalsJade2021-05-131-6/+16
| | | | | | | | Now we will get the type of `[0u8; 4]`.
| * Support length for ByteStringsJade2021-05-131-6/+14
| | | | | | | | I am not confident that my added byte string parsing is right.
| * Add lowering of array lengths in typesJade2021-05-131-4/+4
| | | | | | | | | | | | | | | | | | | | | | Now e.g. ```rust fn a(b: [u8; 2]) { } ``` will know about the length of b.
* | Fix false positive "Missing match arm".Dawer2021-05-141-4/+5
|/
* Merge #8799bors[bot]2021-05-121-6/+20
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | 8799: Add basic support for array lengths in types r=flodiebold a=lf- This recognizes `let a = [1u8, 2, 3]` as having type `[u8; 3]` instead of the previous `[u8; _]`. Byte strings and `[0u8; 2]` kinds of range array declarations are unsupported as before. I don't know why a bunch of our rustc tests had single quotes inside strings un-escaped by `UPDATE_EXPECT=1 cargo t`, but I don't think it's bad? Maybe something in a nightly? Co-authored-by: Jade <[email protected]>
| * address review by @eddybJade2021-05-111-1/+1
| |
| * Add basic support for array lengths in typesJade2021-05-111-6/+20
| | | | | | | | | | | | | | | | | | | | This recognizes `let a = [1u8, 2, 3]` as having type `[u8; 3]` instead of the previous `[u8; _]`. Byte strings and `[0u8; 2]` kinds of range array declarations are unsupported as before. I don't know why a bunch of our rustc tests had single quotes inside strings un-escaped by `UPDATE_EXPECT=1 cargo t`, but I don't think it's bad? Maybe something in a nightly?
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-04 03:30:22 +0000