A modern programming language that makes developers happier.

kotlinlang

Screenshot 2024-10-21 at 14.22.48.png

Is it a new thing in K2 that lambda parameters are by default inferred from the context (not 100% sure what the rule is)? Instead of before it would **not** prefill a parameter name so I could just use `it` everywhere?

Seems a bit verbose for simple `.map{}` or `.filter {}` and my brain is resisting this change but maybe it's for the greater good?

<https://youtrack.jetbrains.com/issue/KTIJ-31631/K2-Completion-always-inserts-lambda-parameter>

&gt; Removing the explicit parameter requires deleting the default selection and also the arrow.
just fyi, I'm pretty sure there's an intent to replace the named argument with an `it`. Maybe it's missing in K2

Screenshot 2024-10-21 at 15.25.04.png

Nope, you're right, it's there :white_check_mark: I'll edit

completion should not insert explicit lambda parameter at the first place. It actually annoys us as well

Yeah yeah agreed, I was just referring to Martin's point in the issue that removing the named argument is more difficult, while there's IDE support for both.