aboutsummaryrefslogtreecommitdiff
path: root/crates/hir_ty/src/infer/expr.rs
Commit message (Collapse)AuthorAgeFilesLines
* clippy::redudant_borrowMaan20032021-06-131-6/+6
|
* Fix coercion in match with expected typeFlorian Diebold2021-06-121-1/+6
| | | | Plus add infrastructure to test type mismatches without expect.
* 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-261-6/+5
|\ | | | | | | | | | | | | | | 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-261-6/+5
| |
* | 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-231-16/+18
|
* Record type mismatches for failed coercions in match etc.Florian Diebold2021-05-211-10/+12
|
* Refactor expectation handlingFlorian Diebold2021-05-211-30/+49
| | | | So as to not use `TyKind::Error` as "no expectation".
* Get rid of resolve_ty_as_possibleFlorian Diebold2021-05-211-13/+15
| | | | Instead use shallow resolving where necessary.
* Rework obligation handlingFlorian Diebold2021-05-211-3/+3
| | | | | | | | 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 if/else coercionFlorian Diebold2021-05-211-1/+4
|
* Remove our unification code, use Chalk's insteadFlorian Diebold2021-05-211-6/+6
|
* internal: Record mismatches of pattern types.Dawer2021-05-191-4/+5
|
* 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.
* 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?
* | Fix inference with conditionally compiled tailsDaniel McNab2021-05-031-1/+1
|/ | | | Fixes #8378
* Move ToChalk -> mappingFlorian Diebold2021-04-091-1/+1
|
* Reorganize hir_ty modulesFlorian Diebold2021-04-091-1/+2
| | | | | Chalk isn't really a 'traits' thing anymore, so it doesn't make sense to have all the Chalk-related stuff in submodules of `traits`.
* CleanupFlorian Diebold2021-04-081-1/+5
|
* Intern SubstitutionsFlorian Diebold2021-04-081-1/+1
| | | | (Costs a bit of performance, reduces memory usage on RA by ~10%.)
* Remove unusedFlorian Diebold2021-04-081-1/+0
|
* Fix shifted_{in,out} callsFlorian Diebold2021-04-081-1/+1
|
* Remove Ty::substs{_mut}Florian Diebold2021-04-071-1/+4
| | | | | | Almost all uses actually only care about ADT substs, so it's better to be explicit. The methods were a bad abstraction anyway since they already didn't include the inner types of e.g. `TyKind::Ref` anymore.
* infer: remove `record_field_resolutions` fieldJonas Schievink2021-04-061-5/+2
| | | | | It stores no useful data, since we can derive all fields from `variant_resolutions`
* Merge #8364bors[bot]2021-04-061-2/+8
|\ | | | | | | | | | | | | | | | | | | 8364: Memory usage improvements r=jonas-schievink a=alexmaco These are mostly focused on splitting up enum variants with large size differences between variants by `Box`-ing things up. In my testing this reduces the memory usage somewhere in the low percentages, even though the measurements are quite noisy. Co-authored-by: Alexandru Macovei <[email protected]>
| * Use Box'es to reduce size of hir_def::expr::Expr from 128 to 72 bytes (on ↵Alexandru Macovei2021-04-061-2/+8
| | | | | | | | | | | | | | | | | | | | 64bit systems) Rationale: only a minority of variants used almost half the size. By keeping large members (especially in Option) behind a box the memory cost is only payed when the large variants are needed. This reduces the size Vec<Expr> needs to allocate.
* | Move Ty accessors to TyExtLukas Wirth2021-04-061-1/+2
| |
* | Add chalk_ir::Const to TyKind::ArrayLukas Wirth2021-04-061-4/+5
| |
* | Use a constructor function for Static lifetimesLukas Wirth2021-04-061-13/+8
| |
* | Add Lifetime to TyKind::RefLukas Wirth2021-04-061-7/+15
|/
* Fix shifting of binders in FnPointerFlorian Diebold2021-04-051-2/+4
| | | | | | | | | - don't shift in/out for Chalk mapping (we want to have the same binders now) - do shift in when creating the signature for a closure (though it shouldn't matter much) - do shift in when lowering a `fn()` type - correctly deal with the implied binder in TypeWalk
* Align FnPointer with ChalkFlorian Diebold2021-04-051-4/+4
|
* Substitution::prefix -> subst_prefixFlorian Diebold2021-04-051-2/+4
| | | | I probably want to get rid of this function completely later.
* Substitution::single -> from1Florian Diebold2021-04-051-2/+4
|
* Move ProjectionTy methods to extension traitFlorian Diebold2021-04-051-2/+2
|
* Add Interner parameter to Binders::substituteFlorian Diebold2021-04-051-6/+8
|
* Binders::subst -> substituteFlorian Diebold2021-04-051-5/+5
|
* Use VariableKinds in BindersFlorian Diebold2021-04-051-2/+2
|
* Move things from `traits` module to `types` as wellFlorian Diebold2021-04-041-3/+3
|
* Move things in hir_ty into submodulesFlorian Diebold2021-04-041-5/+1
| | | | | - all the types that will be replaced by Chalk go to `types` - `TypeWalk` impls go to `walk`
* Replace last uses of SubstsBuilder by TyBuilderFlorian Diebold2021-04-041-2/+1
|
* Some more TyBuilder useFlorian Diebold2021-04-041-29/+25
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-18 00:18:13 +0000