what about changing on `Map lt K V gt ` the `getOrElse` by p

Question

what about changing on `Map lt K V gt ` the `getOrElse` by passing as argument the key which wasn t found ```public inline fun lt K V gt Map lt K V gt getOrElse key K defaultValue gt V V``` to ```public inline fun lt K V gt Map lt K V gt getOrElse key K defaultValue V gt V V``` My use case is to search for the same key somewhere else

ephemient · Answer

you mean ` K gt V` that would be a breaking change note how ```val map = mapOf 3 to fizz 5 to buzz 6 to fizz 9 to fizz 10 to buzz repeat 10 println map getOrElse it + 1 it + 1 toString ``` works now and wouldn t with your proposed signature

elect · Answer

yeah that

Roukanken · Answer

do you really need that Since you already have they key when you are calling the method The only reason I can think of is you want to call already defined method for the default value but you could easily just wrap it with lamda in place you can fairly easily implement this wrapping automatically too ```public inline fun lt K V gt Map lt K V gt getOrElseWithKey key K defaultValue K gt V V = this getOrElse key defaultValue key ```

elect · Answer

we are talking about convenience here

elect · Answer

do I really need that No but it d be comfortable to have it passed as an arg

jimn · Answer

```public fun lt K V gt K getAmong vararg maps Map lt K V gt =maps firstOrNull it containsKey this get this val defaultVal= default thing val firstChoice= the best key val solveUseCase=firstChoice getAmong map1 map2 map3 defaultVal```

elect · Answer

too much noise compared to save the key in a local property confused

ephemient · Answer

from stdlib ```public inline fun lt K V gt Map lt K V gt getOrElse key K defaultValue gt V V = get key defaultValue ``` so your chained lookup is entirely equivalent to ```public fun lt K V gt K getAmong vararg maps Map lt K V gt = maps firstNotNullOfOrNull it this ```

jimn · Answer

fNNOON is comically out of control source code signalling baked into the symbol the function name is probably longer than the emitted instructions face with rolling eyes

ephemient · Answer

definitely longer than the name 48 bytes of bytecode emitted for the most trivial case I tested

jimn · Answer

< ephemient> what nm tool shows bytes on a method this is not shown in the bytecode viewer good catch that a key that points to null may prevent the same key later in the list not pointing to nulls