-
Notifications
You must be signed in to change notification settings - Fork 109
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
Use error-chain to define Ekiden errors #161
Comments
just FYI, you'll need to use |
This is also not a good first issue ;) Turns out that |
Oops :-) |
We should likely use something like the Also see rust-lang-deprecated/failure#287. |
This was done in #1531 (failure is now used everywhere). |
We should use the
error-chain
crate to define our errors inekiden-common
instead of the manual error classes we have now as this seems to be the idiomatic way to do errors in Rust. I already used it to define errors forekiden-tools
in #160 and it seems really nice.The text was updated successfully, but these errors were encountered: