I was wrong, reflecting on the .NET design choices

Re:I was wrong, reflecting on the .NET design choices by poizan42 on Friday April 21, 2017 @07:55PM (#14170349)

I have absolutely no experience with Rust, but I know it normally depends on libunwind, isn't that for unwinding the stack?

[ Parent | on HN ]

Re:I was wrong, reflecting on the .NET design choices by MaulingMonkey on Friday April 21, 2017 @09:08PM (#14170591)

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

But also just to display traces on asserts/panics, even if not "unwound" per se.

[ Parent | on HN ]

Re:I was wrong, reflecting on the .NET design choices by steveklabnik on Saturday April 22, 2017 @02:18AM (#14171326)

By default, rust's panics _do_ unwind the stack. However, you can also set a flag to compile them as an abort instead. Stack traces are still useful in that case.

[ Parent | on HN ]