Move to try_trait_v2 unstable feature #14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
try_traithas now been removed (see rust-lang/rust#42327 (comment)) and replaced withtry_trait_v2. Crate fails to compile with the latest nightly (becauseTry::Okhas been replaced withTry::Output.I have switched to the new
try_trait_v2. Please note that I have taken the liberty of removingtry_fold_resultandtry_rfold_result, giventry_foldandtry_rfoldare now stable (even thoughTrystill requirestry_trait_v2). I could re-instate them if you prefer (although I'm not sure whether to prefer wrapping aResultwith aTry, or the other way around).