Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Use chalk_ir::ClosureId | Florian Diebold | 2021-03-13 | 1 | -1/+2 |
| | |||||
* | Use chalk_ir::FnDefId | Florian Diebold | 2021-03-13 | 1 | -3/+4 |
| | |||||
* | Use chalk_ir::AssocTypeId | Florian Diebold | 2021-03-13 | 1 | -2/+5 |
| | |||||
* | Separate `Ty` and `TyKind` like in Chalk | Florian Diebold | 2021-03-13 | 5 | -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 Schievink | 2021-03-09 | 1 | -1/+1 |
| | |||||
* | Use upstream cov-mark | Laurențiu Nicola | 2021-03-08 | 4 | -12/+7 |
| | |||||
* | Use chalk_ir::AdtId | Lukas Wirth | 2021-03-04 | 2 | -13/+13 |
| | |||||
* | Use chalk_ir::Mutability | Lukas Wirth | 2021-03-01 | 3 | -21/+25 |
| | |||||
* | Introduce Ty::Alias | Lukas Wirth | 2021-03-01 | 3 | -9/+9 |
| | |||||
* | Assert index relationship between type_variable_table and var_unification_table | Lukas Wirth | 2021-03-01 | 1 | -20/+11 |
| | |||||
* | Being Ty::InferenceVar closes to chalk equivalent | Lukas Wirth | 2021-03-01 | 3 | -84/+130 |
| | |||||
* | Merge #7816 | bors[bot] | 2021-02-28 | 2 | -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 struct | Lukas Wirth | 2021-02-28 | 2 | -10/+9 |
| | | |||||
* | | hir_ty: use default type generic for box expressions | cynecx | 2021-02-28 | 1 | -0/+6 |
|/ | |||||
* | Turn Ty::Tuple variant into a tuple-variant | Lukas Wirth | 2021-02-28 | 2 | -5/+5 |
| | |||||
* | Inline TypeCtor into Ty | Lukas Wirth | 2021-02-28 | 4 | -225/+157 |
| | |||||
* | Use chalk_ir::Scalar directly | Lukas Wirth | 2021-02-28 | 1 | -6/+10 |
| | |||||
* | Introduce TypeCtor::Scalar | Lukas Wirth | 2021-02-28 | 2 | -23/+66 |
| | |||||
* | Put the old resolver back | Jonas Schievink | 2021-02-10 | 1 | -3/+8 |
| | |||||
* | infer: update resolver when descending into block | Jonas Schievink | 2021-02-10 | 1 | -16/+20 |
| | |||||
* | Use block_def_map in body lowering | Jonas Schievink | 2021-02-03 | 1 | -1/+1 |
| | |||||
* | Revert "Use block_def_map in body lowering" | Jonas Schievink | 2021-02-02 | 1 | -1/+1 |
| | |||||
* | Use block_def_map in body lowering | Jonas Schievink | 2021-02-01 | 1 | -1/+1 |
| | |||||
* | Handle box with allocator | Thiébaud Weksteen | 2021-01-22 | 1 | -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 keyword | Daiki Ihara | 2021-01-15 | 1 | -0/+7 |
| | |||||
* | Merge #7080 | bors[bot] | 2021-01-01 | 1 | -0/+1 |
|\ | | | | | | | | | | | | | | | 7080: Implement ConstParams for HIR r=Veykril a=Veykril r? @flodiebold Co-authored-by: Lukas Wirth <[email protected]> | ||||
| * | Add ConstParams to the HIR | Lukas Wirth | 2021-01-01 | 1 | -0/+1 |
| | | |||||
* | | Allow spurious warning from rust-lang/rust#80501 | Laurențiu Nicola | 2020-12-30 | 1 | -0/+2 |
|/ | |||||
* | Merge #7021 | bors[bot] | 2020-12-24 | 1 | -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 HIR | Lukas Wirth | 2020-12-24 | 1 | -4/+4 |
| | | |||||
* | | Implement const block inference | Lukas Wirth | 2020-12-23 | 1 | -1/+1 |
| | | |||||
* | | Implement const pat inference | Lukas Wirth | 2020-12-23 | 1 | -1/+5 |
|/ | |||||
* | Ignore lifetime params in substitutions | Lukas Wirth | 2020-12-13 | 1 | -1/+6 |
| | |||||
* | Merge #6818 | bors[bot] | 2020-12-12 | 1 | -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 HIR | Lukas Wirth | 2020-12-11 | 1 | -0/+1 |
| | | |||||
* | | Infer labeled blocks | Lukas Wirth | 2020-12-11 | 1 | -4/+18 |
|/ | |||||
* | Properly infer tuple struct patterns when encountering ellipsis | Lukas Wirth | 2020-11-24 | 1 | -9/+22 |
| | |||||
* | Properly infer tuple patterns when encountering ellipsis | Lukas Wirth | 2020-11-24 | 1 | -8/+17 |
| | |||||
* | Remove more unreachable pubs | Aleksey Kladov | 2020-11-02 | 1 | -1/+1 |
| | |||||
* | Deny unreachable-pub | Aleksey Kladov | 2020-11-02 | 2 | -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 mark | Roland Ruckerbauer | 2020-10-14 | 1 | -0/+3 |
| | |||||
* | Implement binary operator overloading type inference | Roland Ruckerbauer | 2020-10-13 | 1 | -4/+11 |
| | |||||
* | Merge #5971 | bors[bot] | 2020-09-13 | 1 | -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]> | ||||
| * | Implement async blocks | oxalica | 2020-09-10 | 1 | -2/+9 |
| | | |||||
* | | Implement box pattern inference | Jonas Schievink | 2020-09-12 | 1 | -1/+13 |
| | | |||||
* | | Rename record_field_pat to record_pat_field | Pavan Kumar Sunkara | 2020-09-10 | 1 | -1/+1 |
|/ | |||||
* | Rename ra_hir_ty -> hir_ty | Aleksey Kladov | 2020-08-13 | 5 | -0/+2072 |