| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Inline TypeCtor into Ty | Lukas Wirth | 2021-02-28 | 1 | -4/+5 |
| | | |||||
| * | 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 | 1 | -3/+46 |
| | | | | | | | | 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 | 1 | -1/+1 |
| | | |||||
| * | Upgrade Chalk to 0.36 | Florian Diebold | 2020-10-30 | 1 | -11/+10 |
| | | | | | Quite a few changes, because Chalk got rid of the `ApplicationTy` nesting. | ||||
| * | `todo!()` -> `unimplemented!() // FIXME` for CI | Casey Primozic | 2020-10-06 | 1 | -2/+4 |
| | | |||||
| * | Bump chalk to use latest git to get fix | Casey Primozic | 2020-10-06 | 1 | -0/+12 |
| | | | | | * 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 | 1 | -8/+14 |
| | | |||||
| * | Merge #5971 | bors[bot] | 2020-09-13 | 1 | -21/+84 |
| |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 | 1 | -21/+82 |
| | | | |||||
| * | | Lookup ADT and assoc. type names for chalk debug | Nathan Whitaker | 2020-09-09 | 1 | -5/+9 |
| |/ | |||||
| * | 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 | 1 | -0/+586 |
 |
index : rust-analyzer | |
| [FORK] modified to work on wasm targets |
| aboutsummaryrefslogtreecommitdiff |