The Kotlin team is always one step ahead, lol

until someone hits the “these two dependencies share an ancestor” diamond problem

If anyone is interested, I'm creating a library based on Jetpack Compose and context receivers to declare compile-time dependencies between components and automatically inject them at runtime → #decouple

I'm going to (ab)use this knowledge :)

After digging a bit I found at least the usage of

Fir2IrComponents

as a context receiver for utility functions, and then in the classes that contain those components, they're defined like:

class CallAndReferenceGenerator(
    private val components: Fir2IrComponents,
    private val visitor: Fir2IrVisitor,
    private val conversionScope: Fir2IrConversionScope
) : Fir2IrComponents by components

I think there was a time where they were doing that pattern with multiple context-like classes and not just

Fir2IrComponents

, but searching the codebase now it seems that they have everything they need within that class and hence its the only context-like class I could find that's used with that delegation pattern

Turns out

Fir2IrComponents

was introduced in March 2020, way before context receivers were in the language, so it's likely that the usage of delegation there is an artifact of that time and there just hasn't been enough of a reason to change it to using a

context

receiver on the class