Folkert de Vries

well, I figured it out. There were really two syntax problems that this crate cannot parse. one issue is the expression for the length of the array ```rust pub struct...

@tgross35 how do you recommend implementing this? ```rust cfg_if! { if #[cfg(any(target_arch = "sparc", target_arch = "sparc64"))] { s!{ pub struct ptp_clock_caps { pub max_adj: ::c_int, pub n_alarm: ::c_int, pub...

@rustbot review

@rustbot review in the sense that I've made the progress I can I think. CI fails for i686 and I don't know what the problem is there. It looks like...

this was broken up into - https://github.com/rust-lang/libc/pull/4113 - https://github.com/rust-lang/libc/pull/4114 - https://github.com/rust-lang/libc/pull/4128

> In the given example, `break 'foo Some(42);` could be replaced by `Some(42)`. If the goal is to be able to break from a more nested block, maybe a general...

I agree that "a match can be a loop now" is the most unintuitive part of this proposal. I think any proposal tackling this problem will not be entirely obvious...

@workingjubilee > I think it proposes much more: to ascribe a very specific evaluation order to patterns. Otherwise I don't think it works, because without the order being very strict,...

> Note that this RFC does not get borrow checker benefits. (Nor does it claim to, based on my reading of the RFC.) This is not something I considered (so...

> I never like these proposals because labels feel like a last-resort kind of feature in rust, not a first-class one. I agree with the sentiments on macro + label...