3 ms·
I want that stabilized so bad but it's not been really moving forward.
by Sytten 10mo ago
I want that stabilized so bad but it's not been really moving forward.
- mmastrac 10mo agoI was not a fan when I first saw it but I'm becoming desperate to have it the more Rust I write.
- koakuma-chan 10mo ago#![feature(try_blocks)] You only live once.
- dwattttt 10mo agoI've tried it recently, from memory error inference wasn't that great through it.
- JoshTriplett 10mo agoThat's exactly what's currently being fixed before stabilizing it.
- mbrubeck 10mo agoThere's some active work recently on fixing blocking issues, e.g.: https://github.com/rust-lang/rust/pull/148725 https://github.com/rust-lang/rust/pull/148725 https://github.com/rust-lang/rust/pull/149489 https://github.com/rust-lang/rust/pull/149489
- stouset 10mo agoOut of curiosity why can’t a block just do this natively?
- lunar_mycroft 10mo agoBecause then you couldn't use ? to propagate errors if they occurred inside any loops or branches within the function, which would be a significant limitation.
- masklinn 10mo agoBecause it would massively alter langage semantics? It converts returns from the nearest function into returns from the nearest (try) block.