Tracking Issue for Iterator::try_find

[MOZGIII]

Adds try_find to Iterator.

PR: #63177

fn try_find<F, E, R>(&mut self, f: F) -> Result<Option<Self::Item>, E>
where
    F: FnMut(&Self::Item) -> R,
    R: Try<Ok = bool, Error = E>;

Open questions:

• Decide on just-Result, vs potentially supporting Option and other Try types Decide on generic-ness of functions like Iterator::try_find and array::try_map #85115
• Final commenting period (FCP)
• Stabilization PR

[MOZGIII]

I'll start test-running it in the field. The next step for this feature would be to allow coupling the resulting Try type with the closure return type. Apparently, GAT would allow a way to implement this.

[mikeyhew]

Is there an easy workaround to use until this is stabilized?

[MOZGIII]

You can use this crate for now: https://github.com/MOZGIII/iter-try-rs

[mikeyhew]

@MOZGIII thanks. I realized I had a .map call after the .find that I was replacing, so I switched to .filter_map(...).transpose()?