Hacker News Reader

Comment by Deukhoofd | Hacker News Reader

To do so in C# requires messing with C libraries, but generally most behaviour that could actually segfault throws an exception instead.

View on HN

Popping in my mind:

- System.Diagnostics.Debug.Assert (on debug builds)

- Envinroment.FailFast (this is precisely what panic! is usually used for)

- void BlowUp() { BlowUp(); }

But, in reality, any unexpected Exception: how would you properly handle an unexpected NRE or index out of bounds? Either swallowing the exception (bad) or aborting.

panic is just different name for exception though.

Exceptions can be handled, so in rust an "exception" is a "Result<T,U>". A panic means the program terminates, guaranteed. This allows us to ignore hugely difficult edge cases when interacting with hardware / OSes and still ensure the code meets safety guarantees; if the code isn't executing it cannot invalidate any invariants.

> A panic means the program terminates, guaranteed.

That's not strictly true: https://doc.rust-lang.org/std/panic/fn.catch_unwind.html

Panic is what Rust calls exceptions.

> Panic is what Rust calls exceptions.

Not exactly; “panic” is what Go calls exceptions.

Rust “panic!” macro, though, is more of a gentle abort (I guess it's like an uncatchable exception, but that qualifier so radically changes the nature that I can't see it as really the same kind of thing.)

https://doc.rust-lang.org/std/panic/fn.catch_unwind.html

Reply on news.ycombinator.com