[0.6.26] Deprecated type in non-deprecated interface

[matthiasbeyer]

In version 0.6.26, the ErrorKind type got deprecated, but it still appears in the FromExternalError trait, which is not deprecated.

Just wanted to let you know.

I didn't mark this as bug because I am not sure whether you would recognize it as bug.

[epage]

This was intentional. Just #[allow(deprecated)] on those calls until you upgrade. Our hope is there aren't too many.

For other methods like ParserError::from_error_kind, we had to rename the method anyways. This made is so we could deprecate the function and have people call a different one. However, people implementing ParserError still had to implement the deprecated version and use #[allow(deprecated)]. So the other cases weren't completely "free" of this problem.