2 ms·
> Does that mean that there's sometimes a stack trace? Yes. There's a bunch of different bits that come together to cause this, but the core of it is roughly t
by steveklabnik 6y ago
> Does that mean that there's sometimes a stack trace?
Yes. There's a bunch of different bits that come together to cause this, but the core of it is roughly that keeping stack traces adds a cost that not everyone is willing to pay at all times. Rust is trying to figure out how to best accomplish good error handling in an environment that doesn't provide easy answers like "just do it like x at all times."
> Is the presence of a pointer to an error object something that's implementation-specific?
To use the Go parlance, errors are values in Rust. They're not inherently special. There is an interface you can implement if you want interoperability, but Rust only gives you the ability to interoperate, it cannot force you to.