RustyYato
RustyYato
Why doesn't an MIR optimization for the pattern suffice. This looks like something which could be guaranteed for any `loop {match {}}` For example: ``` loop { match op {...
@bors r=@joboet
> Why exactly is it okay for Sender to be Sync? Or basically, how do we boil down the discussion in https://github.com/rust-lang/rust/pull/111087 into a comment for the unsafe impl Sync...
I've updated how enums's tags are specified, now they just defer to whatever `repr(C)`'s tag type is. This is done to reduce the friction of switching from `repr(C)` to `repr(ordered_fields)`....
I have two questions: * How would this work with interior mutability? I.e. would i be able to store a `Cell` in a `const self` field?. * Can you take...
> Just like how rust deals with attempted interior mutability mutations in const variables today. You can not mutate them. > You can get it's reference, and it will be...
I think that there isn't a need to split this feature into `static const self`. Especially since normal `static`s are guaranteed to have a single address. I think just folding...
If you wrap it in a const block, you can still get a 'static reference. https://play.rust-lang.org/?version=stable&mode=debug&edition=2024&gist=162f9612df52864a1e7a3a84ff781200