4 ms·
> 2) No try/catch. Inexcusable in my opinion. You won't like Rust either then. Though its just a matter of time till Rust gets try-catch too. It's slowly movin
by lenkite 4y ago
> 2) No try/catch. Inexcusable in my opinion.
You won't like Rust either then. Though its just a matter of time till Rust gets try-catch too. It's slowly moving towards that step by step. Folks have already made crates https://docs.rs/try-catch/latest/try_catch/ https://docs.rs/try-catch/latest/try_catch/
- Thorentis 4y agoI haven't tried Rust out yet, but the syntax doesn't look appealing. However from what I've seen of the stdlib, it seems to make up for it. If Go had a better stdlib I could probably forgive some syntax problems. But having large gaps in both is very frustrating.
- tragomaskhalos 4y agoThat crate seems to desugar to regular Rust style error handling, ie with Result<>s and ? operators. But I would imagine strong community push-back against any movement towards genuine stack unwind style exception handling in Rust beyond the current panic handling mechanism.
- kaba0 4y agoIt is at least excusable in case of a low-level language meant in part for embedded/kernel development, etc.