Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change Error enum to be more semantically meaningful #84

Open
heartsucker opened this issue Jun 26, 2017 · 2 comments
Open

Change Error enum to be more semantically meaningful #84

heartsucker opened this issue Jun 26, 2017 · 2 comments

Comments

@heartsucker
Copy link
Contributor

I keep tacking stuff on to it, but realistically it should have just an Opaque error type to catch all the IO / HTTP / whatever stuff, and then other values for TUF failures.

@heartsucker
Copy link
Contributor Author

So apparently there's this black magic stuff called error-chain that I should probably be using because omg every time I have to debug a nested error, I want to die.

@tarcieri
Copy link

error-chain is pretty nice for managing boilerplate and automatically generating backtraces

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

No branches or pull requests

2 participants