You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on Attaca I've been using the failure crate for error handling; for various reasons, it's vastly superior to the error-chain crate. Having to integrate error-chain with failure is proving to be problematic, because failure follows the philosophy that errors should be Send + Sync while error-chain maintains simply Send; this results in stuff like the failure::SyncFailure wrapper which puts a non-Sync error into a Mutex to make things safe. This is not cool and should be fixed. Migrating shouldn't be very difficult.
The text was updated successfully, but these errors were encountered:
While working on Attaca I've been using the
failure
crate for error handling; for various reasons, it's vastly superior to theerror-chain
crate. Having to integrateerror-chain
withfailure
is proving to be problematic, becausefailure
follows the philosophy that errors should beSend + Sync
whileerror-chain
maintains simplySend
; this results in stuff like thefailure::SyncFailure
wrapper which puts a non-Sync
error into aMutex
to make things safe. This is not cool and should be fixed. Migrating shouldn't be very difficult.The text was updated successfully, but these errors were encountered: