alt Hacker News> Easy. Always wrap. Wrap with what you were doing when the error occurred.
Then we're back to having stack frames for framework and runtime code in our error traces.
> Easy. Always wrap. Wrap with what you were doing when the error occurred.
Then we're back to having stack frames for framework and runtime code in our error traces.
In my experience doing this, it does not. The wrapping is all yours to write—frameworks and the standard library don’t use it. Their errors would appear as “leaf” errors decorated by the wrapping you, as a team, have added.