You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: text/0000-try-trait-v2.md
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ However, new information has come in since the previous RFC, making people wish
29
29
- An [experience report](https://github.com/rust-lang/rust/issues/42327#issuecomment-366840247) in the tracking issue mentioned that it's annoying to need to make a residual type.
30
30
- The `try {}` conversations have wished for more source information to flow through `?` so that fewer annotations would be required.
31
31
- Similarly, it's no longer clear that `From` should be part of the `?` desugaring for _all_ types. It's both more flexible -- making inference difficult -- and more restrictive -- especially without specialization -- than is always desired.
32
-
- Various library methods, such as `try_map` for arrays ([PR #79713](https://github.com/rust-lang/rust/pull/79713#issuecomment-739075171)), would like to be able to do HKT-like things to produce their result types. (For example, `Iterator::try_find` wants to be able to return a `Foo<Item>` from a predicate that returned a `Foo<bool>`.)
32
+
- Various library methods, such as `try_map` for arrays ([PR #79713](https://github.com/rust-lang/rust/pull/79713#issuecomment-739075171)), would like to be able to do HKT-like things to produce their result types. (For example, `Iterator::try_find` wants to be able to return a `Foo<Option<Item>>` from a predicate that returned a `Foo<bool>`.)
33
33
- Using the "error" terminology is a poor fit for other potential implementations of the trait.
34
34
- It turned out that the current solution accidentally stabilized more interconversion than expected, so a more restricted form may be warranted.
35
35
@@ -49,9 +49,9 @@ Why are we doing this? What use cases does it support? What is the expected outc
0 commit comments