Vladimir Dolzhenko

Context parameters are the biggest change in Kotlin since coroutines! They are already used in Kotlin Compiler, and can be enabled in any project. resources.jetbrains.com/stor… I decided to end my series about new Kotlin features with the one that is likely the most important, well-established, and that will be introduced soon: context parameters. Context parameters are a new implicit way to pass arguments to functions. Those arguments must be part of the scope. Inside functions, we refer to by names, if they are named, or as receivers otherwise. Context parameters are supposed to solve the common problem in DSLs when a function needs more than one receiver, like XXX. You can find plenty of examples of this feature in action in Kotlin Compiler itself. But context parameters also open doors for new possibilities, like implicit receivers passing. That would simplify many FP patterns, like contexts for logging, printing, or other side effects. I have mixed feeling about this feature. It is to me very much Scala-like: opens doors for possibilities, but also for crazy abuses. I remamber saying to one person from Kotlin Language Evolution Team "Please, do not make Kotlin another Scala." Context parameters are quite stable now, you can already use them with a special flag, and they are announced to be introduced in Kotlin 2.2. I explained them in greater detail in my book Functional Kotlin.