-
Notifications
You must be signed in to change notification settings - Fork 13k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename and expose LoopState as ControlFlow #76204
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,67 @@ | ||
use crate::ops::Try; | ||
|
||
/// Used to make try_fold closures more like normal loops | ||
#[unstable(feature = "control_flow_enum", reason = "new API", issue = "75744")] | ||
#[derive(Debug, Clone, Copy, PartialEq)] | ||
pub enum ControlFlow<C, B> { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I have found that There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think it would be confusing to do this without changing the order of the variants as well, and we may as well do that too. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. On consideration, I think a separate PR would be best. |
||
/// Continue in the loop, using the given value for the next iteration | ||
Continue(C), | ||
/// Exit the loop, yielding the given value | ||
Break(B), | ||
} | ||
|
||
#[unstable(feature = "control_flow_enum", reason = "new API", issue = "75744")] | ||
impl<C, B> Try for ControlFlow<C, B> { | ||
type Ok = C; | ||
type Error = B; | ||
#[inline] | ||
fn into_result(self) -> Result<Self::Ok, Self::Error> { | ||
match self { | ||
ControlFlow::Continue(y) => Ok(y), | ||
ControlFlow::Break(x) => Err(x), | ||
} | ||
} | ||
#[inline] | ||
fn from_error(v: Self::Error) -> Self { | ||
ControlFlow::Break(v) | ||
} | ||
#[inline] | ||
fn from_ok(v: Self::Ok) -> Self { | ||
ControlFlow::Continue(v) | ||
} | ||
} | ||
|
||
impl<C, B> ControlFlow<C, B> { | ||
/// Converts the `ControlFlow` into an `Option` which is `Some` if the | ||
/// `ControlFlow` was `Break` and `None` otherwise. | ||
#[inline] | ||
#[unstable(feature = "control_flow_enum", reason = "new API", issue = "75744")] | ||
pub fn break_value(self) -> Option<B> { | ||
match self { | ||
ControlFlow::Continue(..) => None, | ||
ControlFlow::Break(x) => Some(x), | ||
} | ||
} | ||
} | ||
|
||
impl<R: Try> ControlFlow<R::Ok, R> { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Shouldn't the second parameter be There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, definitely. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Oh, I see - we can't do this because it's an unconstrained type parameter. Is there a good way to solve that? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No, the break part here is intentionally the full Maybe leave this particular impl block over in I've been contemplating making a pass through the implementations to use There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Oh, I see. I misunderstood how these were being used. You're right, it's a very strange API. |
||
/// Create a `ControlFlow` from any type implementing `Try`. | ||
#[unstable(feature = "control_flow_enum", reason = "new API", issue = "75744")] | ||
#[inline] | ||
pub fn from_try(r: R) -> Self { | ||
match Try::into_result(r) { | ||
Ok(v) => ControlFlow::Continue(v), | ||
Err(v) => ControlFlow::Break(Try::from_error(v)), | ||
} | ||
} | ||
|
||
/// Convert a `ControlFlow` into any type implementing `Try`; | ||
#[unstable(feature = "control_flow_enum", reason = "new API", issue = "75744")] | ||
#[inline] | ||
pub fn into_try(self) -> R { | ||
match self { | ||
ControlFlow::Continue(v) => Try::from_ok(v), | ||
ControlFlow::Break(v) => v, | ||
} | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hash
and especiallyEq
seem handy, although they are not needed to replaceLoopState
and are less essential forControlFlow
than forOption
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that seems sensible! I don't know when you'd want to hash this but I suppose there's no reason to prevent it.