| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 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 |
 |
index : rust-analyzer | |
| [FORK] modified to work on wasm targets |
| aboutsummaryrefslogtreecommitdiff |