just saw a nice trick to avoid ambiguity about `it` by silencing the latter with `_` ```call.details...

# random

[elect]

just saw a nice trick to avoid ambiguity about it by silencing the latter with _

call.details.map { 
    i18nClient.takeIf { _ -> !it.isMarked }

[Stefan Oltmann]

I don't think this is good style. 🤔

In this case I would go for

call.details.map { detail ->
    i18nClient.takeIf { client -> !detail.isMarked }
}

just to make clear was it is.

[Stefan Oltmann]

Or just

call.details.map { detail ->
    i18nClient.takeIf { !detail.isMarked }
}

[Stefan Oltmann]

I have to admit that I'm not a big fan of using it in general

[elect]

I'd say it depends by the context

[Stefan Oltmann]

In the context of your example it doesn't strike me as good style.

[darkmoon_uk]

I also don't allow it in my code - I always do one of:
• Give a proper label - usually makes the code read much better IMO
• Use a function reference so that there's no exposed lambda to label