Closed silvasch closed 3 months ago
Thanks for your suggestion!
Yes, it should use a qualified path. And, sending a PR is appreciated! since this crate would love to support no_std
, the fully qualified paths should be core::result::Result
instead of std::
one.
Great! I'll submit a PR sometime today.
Implemented in 0.2.0
Hey!
This is an awesome crate.
However, I had one issue, specifically with this piece of code:
This causes compilation to fail, because the
EnumDowncast
derive macro containsResult
(e. g. here) and gets overridden by the customResult
implementation.This would probably be fixed by using the fully qualified path to
Result
in theenum_downcast_derive
crate (Replace everyResult<...>
withstd::result::Result<...>
).If you want, I can open a PR for this.