Result implements FromIterator, so you can move the Result outside and iterators will take care of the rest (including stopping iteration if an error is found).
#[derive(Debug)]
struct Item;
type Id = String;
fn find(id: &Id) -> Result<Item, String> {
Err(format!("Not found: {:?}", id))
}
...
The accepted answer shows how to stop on error while collecting, as requested in the question. However it won't help with large or infinite fallible iterators, or when the iterator is collected by code you don't control. If your use case is one of those, read on.
As already noted, for can be used...
@lyxal funnily enough, just yesterday I was going crazy thinking, "why the hell does Rust have try_fold and try_for_each but no equivalent of Haskell's traverse???", until I found out by dumb luck that oh it's literally just a thing FromIterator implicitly does
Considering how hard it is to find + people not liking to have to turbofish too hard I can't help but think an explicit try_collect or some such could be appropriate too though
(granted I've actually managed to use it without a turbofish more often than not since I happen to be using it in an if let Some( ... ) :D)
And before anyone asks, "wait since when does she actually write Rust?", I'm doing this casual one-week game jam the club's hosting over break, and I'm... writing a massively overengineered localization key system for it before implementing any gameplay or graphics at all
@mousetail'he-him' interesting
yeah I feel like at that point you either want normal collect or to just bite the bullet and write a for loop because you're doing Something Wild
or, like, whatever the take-while is called
because if you're resuming after an error you're probably not treating it that much like an error
By "resuming after an error" it just means it leaves the rest of the items in the iterator. So you can re-use it and get the rest of the items out later if you like
Was doing my laundry this morning, and had to move a load to the dryer that had been left in the washer overnight (as is... often the case here) Noticed a singular popcorn kernel and just laughed about it for a bit; told my sister and she said (paraphrasing) "oh yeah that's probably from the popcorn bag [cloth with drawstrings, not like a paper bag for microwave popcorn lol] I washed" Thought nothing of it as I loaded everything into the dryer fast-forward to 10 minutes ago when I just remembered my wash was probably done like 2 hours ago... there were like 15 or 20 kernels just lined up on…
and then when I finished emptying the dryer I noticed that the bag in question... had its drawstrings tightened...
there were still flecks and crumbs of stuff inside it; she never even turned it inside out
Pressure units are so cursed...you've got: - PSI, which is easy to physically intuit, but uses imperial units - Pascals, which are nice and SI, but impractical - mmHg, which is dependent on the definition of Celsius, the mass of the earth, its sea level, and the density of mercury - Torr, which are like mmHg but off by such a tiny amount you can treat them as interchangeable and feel guilty about it until you go to the grave - Atm, which is 760 torr because why not - Bar, which is defined nicely in terms of Pascals, but with the same mmHg-Torr sorta relationship going on with atm
Result implements FromIterator, so you can move the Result outside and iterators will take care of the rest (including stopping iteration if an error is found).
#[derive(Debug)]
struct Item;
type Id = String;
fn find(id: &Id) -> Result<Item, String> {
Err(format!("Not found: {:?}", id))
}
...
