Context receivers abuse and scope pollution.Contextual classes and contextual constructors.Removing context receiver from the scope with DslMarker.Callable references to contextual functions.Local contextual functions and properties.Alternative approaches and design tradeoffs.Scala given instances and using clauses.

Providing additional context for an action.Providing additional parameters to an action.

Contextual functions and property accessors.

Context receivers and contextual declarations.

We would appreciate hearing your feedback on this proposal in the KEEP-259. It covers a large variety of use cases and was previously known and requested under the name of This is a design proposal for support of context-dependent declarations in Kotlin.

Contributors: Denis Zharkov, Marat Akhin, Mikhail Belyaev, Ilya Gorbunov, Ilmir Usmanov, Simon Ogorodnik,.

Authors: Roman Elizarov, Anastasia Shadrina.

Others, like a JDBC operation, are blocking and therefore will need more thinking: fun processCallAsync(userInput: UserInput): Deferred = async. Then some of the steps will lend themselves naturally to the coroutine approach, like two HTTP requests.

log some information for audit and debug.

write the result of the business logic procedure into the database via JDBC.

make two requests to other endpoints, the order of the requests doesn’t matter.

To meet the requirements for the task we must: Let’s consider a task that might arise during our actual work project.

With context kotlin