| ▲ | Sytten 3 days ago |
| I want that stabilized so bad but it's not been really moving forward. |
|
| ▲ | mbrubeck 2 days ago | parent | next [-] |
| There'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/149489 |
|
| ▲ | mmastrac 3 days ago | parent | prev | next [-] |
| I was not a fan when I first saw it but I'm becoming desperate to have it the more Rust I write. |
|
| ▲ | koakuma-chan 3 days ago | parent | prev | next [-] |
| #![feature(try_blocks)] You only live once. |
| |
| ▲ | dwattttt 2 days ago | parent [-] | | I've tried it recently, from memory error inference wasn't that great through it. | | |
|
|
| ▲ | stouset 2 days ago | parent | prev [-] |
| Out of curiosity why can’t a block just do this natively? |
| |
| ▲ | masklinn 2 days ago | parent | next [-] | | Because it would massively alter langage semantics? It converts returns from the nearest function into returns from the nearest (try) block. | |
| ▲ | lunar_mycroft 2 days ago | parent | prev [-] | | Because 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. |
|
