aboutsummaryrefslogtreecommitdiff
path: root/crates/hir_def/src/expr.rs
Commit message (Collapse)AuthorAgeFilesLines
* Revert "Use block_def_map in body lowering"Jonas Schievink2021-02-021-2/+0
|
* Use block_def_map in body loweringJonas Schievink2021-02-011-0/+2
|
* Use ‘index’ terminology for arena consistentlyAramis Razzaghipour2021-01-171-2/+2
|
* Add support for yiled keywordDaiki Ihara2021-01-151-1/+4
|
* prepare to publish el libro de arenaAleksey Kladov2021-01-141-1/+1
|
* Fixed typos in code commentsVincent Esche2021-01-091-1/+1
|
* Merge #7021bors[bot]2020-12-241-4/+10
|\ | | | | | | | | | | | | | | 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/+10
| |
* | Implement const block inferenceLukas Wirth2020-12-231-1/+7
| |
* | Implement const pat inferenceLukas Wirth2020-12-231-1/+7
|/
* Merge #5971bors[bot]2020-09-131-1/+4
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 blocksoxalica2020-09-101-1/+4
| |
* | Implement box pattern inferenceJonas Schievink2020-09-121-0/+2
|/
* Rename ra_hir_def -> hir_defAleksey Kladov2020-08-131-0/+420