> the for loop syntax should be simple syntactic sugar for iterator.iter().for_each(BODY), not bespoke syntax. The fact this breaks wrecks my mental model. I'm

> the for loop syntax should be simple syntactic sugar for iterator.iter().for_each(BODY), not bespoke syntax. The fact this breaks wrecks my mental model. I'm sorry to be blunt, but this mental model is wrong. .for_each runs a function, while for does not. If what you want is to return early on an error, you can .collect() an Iterator<Item=Result<T, E>> directly into a Result<Vec<T>, E> and then ? that. That's the equivalent of for and ?. Or, you can collect into a Vec<Result<T, E>>. > You must use the for loop syntax if you want to use .await, because iterators are not powerful enough to support real world use-cases. Given that what this requires is async closures, and async closures are an active area of work, this seems like a somewhat unhelpful comment. I definitely agree about having better syntax for iter_mut, though.