News for hackers. Stuff that matters.
Re:Overview of Rust error handling libraries by asdkhadsj on Friday November 22, 2019 @02:12PM (#21608906)
Are you familiar with how costly backtrace is?

I fear bubbling an error up and repeatedly adding a stack trace or some junk like that. Admittedly I have not looked too much into Backtrace, but I hope my concern makes sense.

Re:Overview of Rust error handling libraries by shepmaster on Friday November 22, 2019 @02:25PM (#21609066)
I do believe it's non-zero, as the stack has to be walked and potentially symbols are looked up. The symbols can be delayed until display time, but the stalk walk is "now or never", as I understand it.

SNAFU addresses this by allowing `Option<Backtrace>` in the error struct. The backtrace is only captured when an environment variable is set by the end user.

Re:Overview of Rust error handling libraries by amluto on Friday November 22, 2019 @03:03PM (#21609467)
It would be interesting for someone to port the Linux kernel’s ORC to user code. ORC backtraces are exact and more than an order of magnitude faster than DWARF.
Re:Overview of Rust error handling libraries by DarthGhandi on Sunday November 24, 2019 @02:05AM (#21618904)
> Are you familiar with how costly...

Checks the username of who you responded too: I'll blindly bet yes to that question for any amount you desire.