Originally, SNAFU was going to support no-std, until I learned that the Error trait doesn't exist in libcore!
That being said, people have said that failure works will in no-std. Evidently, failure can just implement Display in this case.
We certainly could do the same, but I wonder if there's some other powers we could add. My wildest thought would be to establish a parallel Error trait that we could implement instead of (or in addition to?) std::error::Error.
Would this be something that ErrorCompat should do?
Originally, SNAFU was going to support no-std, until I learned that the
Errortrait doesn't exist in libcore!That being said, people have said that failure works will in no-std. Evidently, failure can just implement
Displayin this case.We certainly could do the same, but I wonder if there's some other powers we could add. My wildest thought would be to establish a parallel
Errortrait that we could implement instead of (or in addition to?)std::error::Error.Would this be something that
ErrorCompatshould do?