So do I understand correctly that lambdas no longe...

# language-evolution

[Tom]

So do I understand correctly that lambdas no longer have implicit access to context parameters at all? The KEEP and some other places still reference this as an option fairly recently. When was that removed? I must be missing some discussion

[Youssef Shoaib [MOD]]

It's not removed no. Lambdas can't have named context parameters though, so you have to use contextOf<Foo>() if you want the value itself

[Tom]

Yeah but that's a lot more verbose than if they are available implicitly as receivers, such as in the KEEP in §1.8

withConsoleLogger {
  // you can call functions with Logger as context parameter
  logWithTime("doing something")
}

[Tom]

the above appears to no longer work

[CLOVIS]

You can if there is a bridge function

context(logger: Logger)
fun logWithTime(message: String) = logger.logWithTime(message)

[Tom]

Ohh I see, thank you! That seems a bit verbose if you want to make all properties of a context object available in the lambda, but I guess it works

[CLOVIS]

I agree

[Daniel Pitts]

Yikes, I liked context receivers specifically because they reduced boilerplate, but now I've got to add extra boilerplate to do it?

[Youssef Shoaib [MOD]]

Write-once biolerplate though. The point is to have a specialised API surface for context access

[Daniel Pitts]

I can do that without context parameters though.

[Tom]

As far as I can tell currently you still get autocompletions for context-dependent functions if you do not have the relevant context, I hope that at least changes at some point