Vadim Petrochenkov

Copypasting the status from Zulip thread: >I want to look at that PR again (and marked it with waiting on review), but it is time consuming and low priority, so...

@reem > I think labeled return/break is an excellent idea ... I will probably open a separate RFC for it. Please do!

How this is treated during parsing? ``` struct catch { a: u8 } fn main() { let b = 10; catch { a: b } // struct literal or catch...

Also ``` let c1 = catch { a: 10 }; let c2 = catch { ..c1 }; //

Yes, but I'm not sure this belongs to the language reference? It's all about implementation details.

>reference vs a spec Interesting, I always thought those are the same thing. For example, ARM Architecture Reference Manual is a specification.

I observed the same curiosity (followed by a hard assert) on binaries produced by https://github.com/facebookincubator/BOLT. Program header (Phdr) in that case is in a different memory region (different segment?) from...

> TIL that `use *;` is a thing. It's a thing on 2015 edition only, so it's equivalent to `use crate::*;` (maybe rustfmt should normalize it to that).

## Design question: what does the block around the target expression mean? Suppose we have two delegation items ```rust reuse just_expr { self.0 } reuse multi_statements { let x =...

Enabling `--check-cfg=values()` currently incurs some compilation time hit (especially on small programs) because it will load target specifications for all targets (100-200 of them at the moment), while without `--check-cfg=values()`...