-
Notifications
You must be signed in to change notification settings - Fork 138
Using failure
with #![termination_trait]
(fn main() -> Result<T>
)
#130
Comments
The issue you're getting is that you've used I'll leave this open, please report back whether or not you run into more issues, I want to make sure failure works with this feature. |
I tried it using |
It looks like the termination trait requires that we implement the old error type. This is unfortunate. :-( |
Indeed. Although it is still feature-gated. I'm never sure where is the right place to leave comments, but the |
When I finally have some time, I will improve the implementation to support |
Hi, @bkchr, Awesome, thank you. Is this something I could help with? |
It's just changing the implementation, I think we should go the way @withoutboats proposed by restricting the type to |
Niko's recent "hacking on the compiler" writings inspired me to try building the compiler... So I forked rust and built it for the first time 🎉. I ran https://github.com/U007D/rust/commit/b9b2ca8bd04e932a361adff2af813bd0f9f07e54 Assuming this diff looks right to you two, where should I target the PR? Back to rust-lang/rust/master? Or are you working from a branch that I should merge back to, @bkchr? |
@U007D Back to |
Done. |
Relax termination_trait's error bound As per [this conversation](https://github.com/withoutboats/failure/issues/130#issuecomment-358572413) with @withoutboats and @bkchr
I'm running into a couple of issues trying to use
failure
with#![termination_trait]
.results in:
Switching the
Result
declaration totype Result<T> = std::result::Result<T, FailureError>
yields:Is there a solution for this? If not, should this be a
failure
or atermination_trait
issue?Many thanks,
U007D
The text was updated successfully, but these errors were encountered: