You can find more information here https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/lazy.html

Koin inject implemented as

inline fun <reified T : Any> ComponentCallbacks.inject(
        qualifier: Qualifier? = null,
        noinline parameters: ParametersDefinition? = null
) = lazy { get<T>(qualifier, parameters) }

That is the same

lazy(LazyThreadSafetyMode.SYNCHRONIZED) {
    get<T>(qualifier, parameters)
}

That implementation has impact on performance

We need options to use unsafe lazy (

lazy(LazyThreadSafetyMode.NONE)

) for injecting

It’s not good always use synchronization

on one side, we don’t know if current environment is running multithread or not

but the other, we lock instance resolution in the tree ... then we should not be exposed to problem

and then we would allow LazyThreadSafetyMode.NONE

Resolution of an instance must be locked inside depencies tree, not via lazy resolution from client side (via lazy delegate)

I’m reworking internal engine to clearly optimize just to lock in on tree resolution

I can create issue for that on Github

Do you need it?

I can make some work around it directly 😉

I’m reworking internal engine to clearly optimize just to lock in on tree resolution

You need to lock only

scoped

and

single

dependncies, because factory need to be created every time and no need to lock thread for resolution

check

SingleInstanceFactory

&

FactoryInstanceFactory

Done