Hi, why calling `thenApply` like this is possible ...

# announcements

[jakub.dyszkiewicz]

Hi, why calling thenApply like this is possible

CompletableFuture.completedFuture("x").thenApply { it }

but second version with executor

CompletableFuture.completedFuture("x").thenApply({ it }, Executors.newCachedThreadPool())

throws compilation error and I have to do something like this

CompletableFuture.completedFuture("x").thenApply(java.util.Function<String, String> { it }, Executors.newCachedThreadPool())

[leosan]

just a guess, I haven’t tried myself, but try like this

CompletableFuture.completedFuture(“x”).thenApplyAsync({ it }) { Executors.newCachedThreadPool() }

[jakub.dyszkiewicz]

thenApply does not receive two functions, just one and executor, so this is not correct

[leosan]

oh sorry, I used thenApplyAsync i see

[mzgreen]

I think it’s because the first argument is eligible for SAM -> lambda conversion. And Kotlin either wants all two arguments as lambdas or none of them.

[leosan]

and the second i{} s not a function is just a kotlin syntax sugar for the last parameter