aboutsummaryrefslogtreecommitdiff
path: root/crates/hir_def/src/body
Commit message (Collapse)AuthorAgeFilesLines
* Revert "Make use of `block_def_map` in body lowering"Jonas Schievink2021-01-211-12/+4
|
* Make use of `block_def_map` in body loweringJonas Schievink2021-01-211-4/+12
| | | | | Removes the `local_scope` hack from `Expander` in favor of tracking the `DefMap` in use during body lowering
* Add support for yiled keywordDaiki Ihara2021-01-151-0/+4
|
* prepare to publish el libro de arenaAleksey Kladov2021-01-142-2/+2
|
* Fixed typos in code commentsVincent Esche2021-01-091-2/+2
|
* Change <|> to $0 - RebaseKevaundray Wedderburn2021-01-071-15/+15
|
* Rename expr -> tail_exprAleksey Kladov2021-01-051-1/+1
|
* Merge #7021bors[bot]2020-12-241-47/+45
|\ | | | | | | | | | | | | | | 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-47/+45
| |
* | Implement const block inferenceLukas Wirth2020-12-231-0/+4
| |
* | Implement const pat inferenceLukas Wirth2020-12-231-3/+9
|/
* Update ungrammar for const block patternsLukas Wirth2020-12-231-1/+3
|
* Refactor attributes API to allow handling cfg_attrJonas Schievink2020-12-181-1/+1
|
* Node-ify lifetimesLukas Wirth2020-12-161-17/+7
|
* Make macro def krate mandatoryJonas Schievink2020-12-151-1/+1
| | | | Refactors builtin derive support to go through proper name resolution
* Basic support for decl macros 2.0Jonas Schievink2020-12-151-1/+4
|
* Move to upstream `macro_rules!` modelJonas Schievink2020-12-151-65/+69
|
* Expand statements for mbe in loweringEdwin Cheng2020-12-151-82/+134
|
* Add test for `$crate` in builtin macrosJonas Schievink2020-12-081-0/+28
| | | | Fixes #6716
* Make `compile_error!` message match upstream rustcJonas Schievink2020-12-031-1/+1
| | | | It only consists of the argument passed to it
* Make `compile_error!` lazy and emit a diagnosticJonas Schievink2020-12-031-0/+6
|
* Give better diagnostic if `OUT_DIR` is unsetJonas Schievink2020-12-031-0/+3
|
* Update/Fix testsJonas Schievink2020-12-031-4/+15
|
* Test macro diagnostics in body loweringJonas Schievink2020-12-021-0/+41
|
* Attach macro expansion errors to the right fileJonas Schievink2020-12-021-2/+5
|
* Emit unresolved proc macro errorsJonas Schievink2020-12-012-9/+28
|
* Emit macro diagnostics when lowering bodiesJonas Schievink2020-11-302-3/+17
|
* Cleanup APIAleksey Kladov2020-11-061-10/+11
|
* Remove more unreachable pubsAleksey Kladov2020-11-021-2/+2
|
* Deny unreachable-pubAleksey Kladov2020-11-021-3/+3
| | | | | | | | 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.
* Diagnose #[cfg]s in bodiesJonas Schievink2020-10-233-14/+141
|
* Fix `mut self` not emitting mutable binding on `self` useLukas Wirth2020-10-111-1/+4
|
* 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-1/+5
|/
* :arrow_up: ungrammarAleksey Kladov2020-08-211-1/+1
|
* Rename ra_hir_def -> hir_defAleksey Kladov2020-08-132-0/+1387
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-02 20:16:55 +0000