On 23/06/14 01:15 AM, comex wrote: > On Mon, Jun 23, 2014 at 1:05 AM, Daniel Micay <danielmi...@gmail.com> wrote: >> The call we make to perform unwinding isn't a pure function though, it's >> aware of the context causing it to unwind. As long as we're supporting >> stuff like backtraces outside of a debugger, that's going to be the case. > > It does not seem essential to me that backtraces be 100% accurate in > optimized builds - at least judging by how people manage to get by > with the utter crap that is most compilers' optimized debugging info > :P > > Not sure exactly what you're referring to, though.
I'm referring the code performing failure in Rust being impure (not readnone or readonly) in addition to being able to unwind (not nounwind).
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
