scottmcm

Wow, that's far more results for npot-1 than I would have guessed!

Related: https://internals.rust-lang.org/t/simple-partial-application/7685/22?u=scottmcm I think I'm far more fond of _only_ doing the one-argument-used-once cases, which don't have the "where's the end of the lambda?" problem as much. And since this...

> So the (AFAICT very common) case of just needing the behavior of a single binary operator is already well-served by simply passing the trait method instead of creating an...

> Feels more functional, less ad-hoc, and to be honest, less scary. Can you elaborate on that feeling? To me it seems like it's weird for ```rust it.map(|x| str::len(x)) ```...

I think de-RFCing the local variables part of this makes sense. The original FCP was > I am not recommending an experimental RFC because I don't think we'll be making...

@Noratrieb Do you have what you need to address the [concern](https://github.com/rust-lang/rfcs/pull/3829#issuecomment-2941831706) above? AFAICT the RFC hasn't been updated since that was filed.

Is there any iteraction with https://doc.rust-lang.org/stable/std/process/struct.ExitCode.html that could make sense here? Since that type is itself about how the correct type for an exit code is not just an i32....

Thanks! I'm glad to have these, since I think they're the only good shifts :) @bors r+ rollup

> Can you create an equivalent method that turns `Iterator` into `Option`? It's literally [impossible](https://users.rust-lang.org/t/flat-map-on-an-iterator-of-results/77605/4?u=scottmcm) to make such a method that's lazy. And if you're fine with `Iterator` → `Option`,...

I'm happy to say we're not going to *immediately dismiss* a proposal for `is` just based on the existence of `let` chains. It's not dispositive *on its own*. That said,...