Coordinate with the various stakeholder of the error crates

[roblabla]

This crate is meant to be a port of the std::error::Error trait that various error crates (such as fehler, failure and snafu, to name a few) can depend on to ensure they can properly interoperate in no_std environment. In order to achieve this dream of interoperability, we should ensure everyone is on-board with the plan. Here are the currently identified stakeholders.

• snafu
  • Use a separate core-error crate to provide the Error trait on no-std shepmaster/snafu#184
  • Currently has no-std support on master. Works with a hidden Error trait that users can't implement directly.
• failure
  • Integration work started at Replace std::error::Error with core_error::Error rust-lang-deprecated/failure#334
  • Collaborate on a "core::Error" crate with snafu, anyhow and other error crates rust-lang-deprecated/failure#328
  • Has no_std support through its own Fail trait. Disables the std error compat layer in nostd.
• anyhow
  • Collaborate on a "core::Error" crate with snafu dtolnay/anyhow#9
  • No no_std support thus far.
• error-chain
  • no_std support rust-lang-deprecated/error-chain#138
  • No no-std support thus far. It has been discussed

No longer relevant:

• fehler
  • Is going to strip out all the Error trait related functionality from fehler, delegating them to anyhow.
  • Collaborate on a "core::Error" crate with snafu, anyhow and other error crates withoutboats/fehler#24

[leo60228]

I have a WIP snafu branch at https://github.com/core-error/snafu/tree/core-error.

[roblabla]

Made a failure Draft PR: rust-lang-deprecated/failure#334

[jplatte]

Is progress happening still?

anyhow does have no_std support now by the way.

[roblabla]

It’s still on my radar but I have been neglecting finishing this up. I still need to re-review the current public API, add the new rust versions to CI, make sure there’s no error missing and it should be good to go for 1.0.0. The last real “blocker” issue is #8.