Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Don't use Substs for Ref/Raw/Array/Slice | Florian Diebold | 2021-03-14 | 1 | -17/+13 |
| | |||||
* | Make Ty wrap TyKind in an Arc | Florian Diebold | 2021-03-14 | 1 | -1/+1 |
| | | | | | | | | ... 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. | ||||
* | More renaming | Florian Diebold | 2021-03-14 | 1 | -10/+8 |
| | |||||
* | Use chalk_ir::FnSig | Florian Diebold | 2021-03-14 | 1 | -10/+9 |
| | |||||
* | Rename some fields to their Chalk names | Florian Diebold | 2021-03-14 | 2 | -13/+13 |
| | |||||
* | Move type lowering methods to TyLoweringContext | Florian Diebold | 2021-03-13 | 1 | -1/+1 |
| | |||||
* | Use chalk_ir::OpaqueTyId | Florian Diebold | 2021-03-13 | 2 | -26/+9 |
| | |||||
* | Use chalk_ir::PlaceholderIndex | Florian Diebold | 2021-03-13 | 1 | -19/+3 |
| | |||||
* | Use chalk_ir::ClosureId | Florian Diebold | 2021-03-13 | 2 | -11/+6 |
| | |||||
* | Use chalk_ir::FnDefId | Florian Diebold | 2021-03-13 | 3 | -6/+4 |
| | |||||
* | Use chalk_ir::AssocTypeId | Florian Diebold | 2021-03-13 | 3 | -47/+26 |
| | |||||
* | Use chalk_ir::ForeignDefId | Florian Diebold | 2021-03-13 | 2 | -23/+2 |
| | |||||
* | Separate `Ty` and `TyKind` like in Chalk | Florian Diebold | 2021-03-13 | 2 | -58/+65 |
| | | | | | Currently `Ty` just wraps `TyKind`, but this allows us to change most places to already use `intern` / `interned`. | ||||
* | Simplify a bit | Florian Diebold | 2021-03-12 | 1 | -10/+5 |
| | |||||
* | Use Chalk Environment more directly | Florian Diebold | 2021-03-12 | 2 | -35/+7 |
| | |||||
* | Delete `ContainerId` | Jonas Schievink | 2021-03-09 | 1 | -2/+2 |
| | |||||
* | Use chalk_ir::AdtId | Lukas Wirth | 2021-03-04 | 2 | -22/+8 |
| | |||||
* | Use chalk_ir::Mutability | Lukas Wirth | 2021-03-01 | 1 | -22/+6 |
| | |||||
* | Introduce Ty::Alias | Lukas Wirth | 2021-03-01 | 2 | -15/+15 |
| | |||||
* | Being Ty::InferenceVar closes to chalk equivalent | Lukas Wirth | 2021-03-01 | 1 | -22/+10 |
| | |||||
* | Lift FnPointer into a struct | Lukas Wirth | 2021-02-28 | 2 | -19/+14 |
| | |||||
* | Remove Substs from Ty::ForeignType | Lukas Wirth | 2021-02-28 | 1 | -5/+4 |
| | |||||
* | Turn Ty::Tuple variant into a tuple-variant | Lukas Wirth | 2021-02-28 | 1 | -2/+2 |
| | |||||
* | Inline TypeCtor into Ty | Lukas Wirth | 2021-02-28 | 2 | -108/+90 |
| | |||||
* | Use chalk_ir::Scalar directly | Lukas Wirth | 2021-02-28 | 1 | -60/+4 |
| | |||||
* | Introduce TypeCtor::Scalar | Lukas Wirth | 2021-02-28 | 1 | -80/+60 |
| | |||||
* | Update crates | kjeremy | 2021-02-08 | 1 | -2/+3 |
| | | | | Pulls in https://github.com/rust-lang/chalk/pull/682 | ||||
* | Bump chalk | Laurențiu Nicola | 2021-02-02 | 1 | -2/+2 |
| | |||||
* | Make `ModuleId`'s `krate` field private | Jonas Schievink | 2021-01-22 | 1 | -2/+2 |
| | |||||
* | Bump chalk | Laurențiu Nicola | 2020-12-23 | 1 | -2/+9 |
| | |||||
* | Upgrade Chalk | Florian Diebold | 2020-12-07 | 3 | -6/+72 |
| | | | | | | | Also make overflow depth and max type size configurable through env variables. This can be helpful at least for debugging. Fixes #6628. | ||||
* | Remove more unreachable pubs | Aleksey Kladov | 2020-11-02 | 3 | -19/+19 |
| | |||||
* | Deny unreachable-pub | Aleksey Kladov | 2020-11-02 | 1 | -27/+27 |
| | | | | | | | | 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. | ||||
* | Upgrade Chalk to 0.36 | Florian Diebold | 2020-10-30 | 4 | -316/+176 |
| | | | | Quite a few changes, because Chalk got rid of the `ApplicationTy` nesting. | ||||
* | Get rid of FAKE_PLACEHOLDER | Florian Diebold | 2020-10-25 | 1 | -8/+9 |
| | | | | | The lifetime placeholder can be replaced by the static lifetime, and for array sizes we should just be using a concrete const. | ||||
* | Make unimplemented match variants explicit | Casey Primozic | 2020-10-07 | 1 | -1/+2 |
| | |||||
* | `todo!()` -> `unimplemented!() // FIXME` for CI | Casey Primozic | 2020-10-06 | 2 | -3/+5 |
| | |||||
* | Bump chalk to use latest git to get fix | Casey Primozic | 2020-10-06 | 2 | -0/+13 |
| | | | | * Chalk very recently (like an hour ago) merged a fix that prevents rust analyzer from panicking. This allows it to be usable again for code that hits those situations. See #6134, #6145, Probably #6120 | ||||
* | Update chalk to 0.28.0 | Bram van den Heuvel | 2020-09-25 | 1 | -2/+8 |
| | |||||
* | Update chalk to 0.27 and adapt to chalk changes. | Charles Lew | 2020-09-15 | 4 | -27/+76 |
| | |||||
* | Merge #5971 | bors[bot] | 2020-09-13 | 2 | -21/+87 |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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]> | ||||
| * | Fix and prettify comments | oxalica | 2020-09-11 | 1 | -4/+6 |
| | | |||||
| * | Implement async blocks | oxalica | 2020-09-10 | 2 | -21/+85 |
| | | |||||
* | | Tweak interner for chalk | Nathan Whitaker | 2020-09-09 | 1 | -9/+9 |
| | | |||||
* | | Lookup ADT and assoc. type names for chalk debug | Nathan Whitaker | 2020-09-09 | 2 | -5/+21 |
|/ | |||||
* | Lookup adt names | Wilco Kusee | 2020-08-14 | 1 | -1/+2 |
| | |||||
* | Print chalk programs in debug output | Wilco Kusee | 2020-08-14 | 1 | -10/+12 |
| | |||||
* | Rename ra_hir_ty -> hir_ty | Aleksey Kladov | 2020-08-13 | 4 | -0/+2114 |