Skip to content
This repository has been archived by the owner on Sep 10, 2022. It is now read-only.

annotate errors #11

Merged
merged 1 commit into from
Jan 10, 2019
Merged

annotate errors #11

merged 1 commit into from
Jan 10, 2019

Conversation

Stebalien
Copy link
Member

@anacrolix
Copy link

@Stebalien
Copy link
Member Author

@anacrolix maybe... It looks like that package records a stack trace. Generating stack traces for errors can get a bit expensive. We'd have to carefully profile that before using it.

Ideally, it would provide an option to disable collecting stacks. I wonder if they'll accept a PR.

@Stebalien Stebalien merged commit 208c6f3 into master Jan 10, 2019
@ghost ghost removed the status/in-progress In progress label Jan 10, 2019
@anacrolix
Copy link

The errors.WithMessage function handles that.

@Stebalien
Copy link
Member Author

I see. However, it still adds stack traces by default everywhere else. If we're going to pick a third-party errors library (we should, IMO), I'd like to use it everywhere for. Otherwise, nice features like Cause aren't very useful.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants