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

Investigate failure to replace error-chain #234

Closed
Keats opened this Issue Nov 23, 2017 · 2 comments

Comments

2 participants
@Keats
Owner

Keats commented Nov 23, 2017

https://github.com/withoutboats/failure

Probably a bit too early right now but soon

@stephanbuys

This comment has been minimized.

Show comment
Hide comment
@stephanbuys

stephanbuys Nov 24, 2017

For what it's worth - it was very painless for me - the only rough edges were some errors returned by tera weren't Sync (or was it Send?), so I just opted for a match, then Option returns a value, NoneType(?) which doesn't have Display implemented - so there I had a special case too. Otherwise it was a pleasure. I would highly recommend moving to Failure before 1.x.

stephanbuys commented Nov 24, 2017

For what it's worth - it was very painless for me - the only rough edges were some errors returned by tera weren't Sync (or was it Send?), so I just opted for a match, then Option returns a value, NoneType(?) which doesn't have Display implemented - so there I had a special case too. Otherwise it was a pleasure. I would highly recommend moving to Failure before 1.x.

@Keats

This comment has been minimized.

Show comment
Hide comment
@Keats

Keats Sep 3, 2018

Owner

Failure doesn't seem to be the way to go for the foreseeable future right now.

Owner

Keats commented Sep 3, 2018

Failure doesn't seem to be the way to go for the foreseeable future right now.

@Keats Keats closed this Sep 3, 2018

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