aboutsummaryrefslogtreecommitdiff
path: root/crates/hir_ty/src/infer
Commit message (Collapse)AuthorAgeFilesLines
...
| * Make Ty wrap TyKind in an ArcFlorian Diebold2021-03-144-10/+10
| | | | | | | | | | | | | | | | ... 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.
* | Simplify source maps for fieldsAleksey Kladov2021-03-151-3/+2
|/
* Use chalk_ir::FnSigFlorian Diebold2021-03-141-1/+1
|
* Rename some fields to their Chalk namesFlorian Diebold2021-03-142-5/+5
|
* Move type lowering methods to TyLoweringContextFlorian Diebold2021-03-131-5/+5
|
* Use chalk_ir::OpaqueTyIdFlorian Diebold2021-03-131-3/+4
|
* Use chalk_ir::PlaceholderIndexFlorian Diebold2021-03-131-1/+1
|
* Use chalk_ir::ClosureIdFlorian Diebold2021-03-131-1/+2
|
* Use chalk_ir::FnDefIdFlorian Diebold2021-03-131-3/+4
|
* Use chalk_ir::AssocTypeIdFlorian Diebold2021-03-131-2/+5
|
* Separate `Ty` and `TyKind` like in ChalkFlorian Diebold2021-03-135-186/+239
| | | | | Currently `Ty` just wraps `TyKind`, but this allows us to change most places to already use `intern` / `interned`.
* Stop using `ContainerId` in `AssocContainerId`Jonas Schievink2021-03-091-1/+1
|
* Use upstream cov-markLaurențiu Nicola2021-03-084-12/+7
|
* Use chalk_ir::AdtIdLukas Wirth2021-03-042-13/+13
|
* Use chalk_ir::MutabilityLukas Wirth2021-03-013-21/+25
|
* Introduce Ty::AliasLukas Wirth2021-03-013-9/+9
|
* Assert index relationship between type_variable_table and var_unification_tableLukas Wirth2021-03-011-20/+11
|
* Being Ty::InferenceVar closes to chalk equivalentLukas Wirth2021-03-013-84/+130
|
* Merge #7816bors[bot]2021-02-282-10/+9
|\ | | | | | | | | | | | | | | 7816: Lift Ty::Fn into a struct r=Veykril a=Veykril bors r+ Co-authored-by: Lukas Wirth <[email protected]>
| * Lift FnPointer into a structLukas Wirth2021-02-282-10/+9
| |
* | hir_ty: use default type generic for box expressionscynecx2021-02-281-0/+6
|/
* Turn Ty::Tuple variant into a tuple-variantLukas Wirth2021-02-282-5/+5
|
* Inline TypeCtor into TyLukas Wirth2021-02-284-225/+157
|
* Use chalk_ir::Scalar directlyLukas Wirth2021-02-281-6/+10
|
* Introduce TypeCtor::ScalarLukas Wirth2021-02-282-23/+66
|
* Put the old resolver backJonas Schievink2021-02-101-3/+8
|
* infer: update resolver when descending into blockJonas Schievink2021-02-101-16/+20
|
* Use block_def_map in body loweringJonas Schievink2021-02-031-1/+1
|
* Revert "Use block_def_map in body lowering"Jonas Schievink2021-02-021-1/+1
|
* Use block_def_map in body loweringJonas Schievink2021-02-011-1/+1
|
* Handle box with allocatorThiébaud Weksteen2021-01-221-1/+4
| | | | | | | | In 1.49.0, the definition of Box was modified to support an optional Allocator[1]. Adapt the parsing of the `box` keyword to supply the expected number of parameters to the constructor. [1] https://github.com/rust-lang/rust/commit/f288cd2e179f600fa00c2a407206a12f6c5a91e0
* Add support for yiled keywordDaiki Ihara2021-01-151-0/+7
|
* Merge #7080bors[bot]2021-01-011-0/+1
|\ | | | | | | | | | | | | | | 7080: Implement ConstParams for HIR r=Veykril a=Veykril r? @flodiebold Co-authored-by: Lukas Wirth <[email protected]>
| * Add ConstParams to the HIRLukas Wirth2021-01-011-0/+1
| |
* | Allow spurious warning from rust-lang/rust#80501Laurențiu Nicola2020-12-301-0/+2
|/
* Merge #7021bors[bot]2020-12-241-4/+4
|\ | | | | | | | | | | | | | | 7021: Track labels in the HIR r=matklad a=Veykril Groundwork for #6966 Co-authored-by: Lukas Wirth <[email protected]>
| * Track labels in the HIRLukas Wirth2020-12-241-4/+4
| |
* | Implement const block inferenceLukas Wirth2020-12-231-1/+1
| |
* | Implement const pat inferenceLukas Wirth2020-12-231-1/+5
|/
* Ignore lifetime params in substitutionsLukas Wirth2020-12-131-1/+6
|
* Merge #6818bors[bot]2020-12-121-0/+1
|\ | | | | | | | | | | | | | | | | | | 6818: Add Lifetimes to the HIR r=matklad a=Veykril This doesn't handle resolve yet as I don't know yet how that will be used. I'll get to that once I start moving the lifetime reference PR to the hir. This also adds a new `hir` name type for lifetimes and labels, `hir::LifetimeName`. Co-authored-by: Lukas Wirth <[email protected]>
| * Add Lifetimes to the HIRLukas Wirth2020-12-111-0/+1
| |
* | Infer labeled blocksLukas Wirth2020-12-111-4/+18
|/
* Properly infer tuple struct patterns when encountering ellipsisLukas Wirth2020-11-241-9/+22
|
* Properly infer tuple patterns when encountering ellipsisLukas Wirth2020-11-241-8/+17
|
* Remove more unreachable pubsAleksey Kladov2020-11-021-1/+1
|
* Deny unreachable-pubAleksey Kladov2020-11-022-14/+23
| | | | | | | | It's very useful when `pub` is equivalent to "this is crate's public API", let's enforce this! Ideally, we should enforce it for local `cargo test`, and only during CI, but that needs https://github.com/rust-lang/cargo/issues/5034.
* binary operator overload type inference: add test markRoland Ruckerbauer2020-10-141-0/+3
|
* Implement binary operator overloading type inferenceRoland Ruckerbauer2020-10-131-4/+11
|
* Merge #5971bors[bot]2020-09-131-2/+9
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5971: Implement async blocks r=flodiebold a=oxalica Fix #4018 @flodiebold already gave a generic guide in the issue. Here's some concern about implementation detail: - Chalk doesn't support generator type yet. - Adding generator type as a brand new type (ctor) can be complex and need to *re-introduced* builtin impls. (Like how we implement closures before native closure support of chalk, which is already removed in #5401 ) - The output type of async block should be known after type inference of the whole body. - We cannot directly get the type from source like return-positon-impl-trait. But we still need to provide trait bounds when chalk asking for `opaque_ty_data`. - During the inference, the output type of async block can be temporary unknown and participate the later inference. `let a = async { None }; let _: i32 = a.await.unwrap();` So in this PR, the type of async blocks is inferred as an opaque type parameterized by the `Future::Output` type it should be, like what we do with closure type. And it really works now. Well, I still have some questions: - The bounds `AsyncBlockImplType<T>: Future<Output = T>` is currently generated in `opaque_ty_data`. I'm not sure if we should put this code here. - Type of async block is now rendered as `impl Future<Output = OutputType>`. Do we need to special display to hint that it's a async block? Note that closure type has its special format, instead of `impl Fn(..) -> ..` or function type. Co-authored-by: oxalica <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2024-08-24 11:44:33 +0100