No-Panic Rust: A Nice Technique for Systems Programming
blog.reverberate.org
No-Panic Rust: A Nice Technique for Systems Programming
1–10 of 143 posts
Re: No-Panic Rust: A Nice Technique for Systems Programming
#2Re: No-Panic Rust: A Nice Technique for Systems Programming
#3Re: No-Panic Rust: A Nice Technique for Systems Programming
#4This seems..absurd for a programming language with goals like Rust. Why isn't this a compiler option? Just set -nopanics and the compiler errors and flags anything which is pulling in a panic at the very least?
It also feels like most of the pains on avoiding panics centers around allocations which, though a bit unfortunate, makes sense; it was an intentional design choice to make allocations panic instead of return Results, because most users of the language would probably crash on allocation fails anyways and it would introduce a lot of clutter. There was some effort some while ago on having better fallible allocations, but I'm not sure what happened over there.
Re: No-Panic Rust: A Nice Technique for Systems Programming
#5Re: No-Panic Rust: A Nice Technique for Systems Programming
#6This website makes by browser freeze... No idea why. Not able to read the article.
Re: No-Panic Rust: A Nice Technique for Systems Programming
#7Re: No-Panic Rust: A Nice Technique for Systems Programming
#8This seems..absurd for a programming language with goals like Rust. Why isn't this a compiler option? Just set -nopanics and the compiler errors and flags anything which is pulling in a panic at the very least?
``` [profile.release] panic = 'abort' ```
Re: No-Panic Rust: A Nice Technique for Systems Programming
#9Panics really seem bad for composability. And relying on the optimzer here seems like a fragile approach.
(And how is there no -nopanic compiler flag?)
Re: No-Panic Rust: A Nice Technique for Systems Programming
#10This website makes by browser freeze... No idea why. Not able to read the article.