Making errors Sync

[withoutboats]

The failure crate requires that errors are Sync. Currently (but not in all previous versions) error-chain makes errors which are !Sync (because they have a Box<Error + Send> inside them).

It would be beneficial IMO to:

1. Provide a Sync adapter for errors. (This could be optimized to not actually use a Mutex except in the Box case, if you think its warranted).
2. Release a breaking change which reverts back to requiring Sync by default. This is probably at least a little controversial.

[bvinc]

I believe I'm being hit by a problem of my errors being !Sync. I'm implementing Read and Write, so I'm trying to wrap my errors in an io::Error. This should be easy, but it's impossible if my error is !Sync, because io:Error requires it to be Sync.

[tazjin]

This would be beneficial for those that don't want to lose the type-safety of error-chain but have to interface with crates using failure!

[jnicholls]

Agreed, wish there was at least an adapter out of the box. I'm having to translate my errors at the moment and it's a hassle :D

[rustonaut]

I just run into this too it's quite a bumper and very depressing if it's
in a (opt) dependency and you have to have Sync errors because of
another dependency/software architecture/...

[jnicholls]

I fully switched to failure as I find it to be a more robust and cross-cutting approach than error_chain that doesn’t do as much wrapping of dependency error types but instead promotes that you maintain your own errors and contexts, particularly when culminating many libs together into an application and working with all the error types.

On Thu, May 31, 2018 at 8:12 AM Philipp Korber ***@***.***> wrote: I just run into this too it's quite a bumper and very depressing if it's in a (opt) dependency and you have to have Sync errors because of another dependency/software architecture/... — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#240 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABPq0PhtK0QZO4NxOKqK3o4vEbsXVnwks5t394ngaJpZM4QXLNc> .

-- Sent from Gmail Mobile

[elichai]

Any news about this?
This cause a lot of troubles if you use failure::Error but use a library that uses error-chain