Concretely, maybe this line can be rewritten? If using T::class can be avoided, there's no need for the function to be reified, thus allowing it to be used in non-inline generic functions.
My use case is as follows: we are building a internal library where we want to write a class that handles certain operations with a MongoDB database, but the concrete type can vary between different usages of the library. It is impossible to write this class using inline functions and reified generics, so we must use non-reified functions.
I'd would like to ask why this function is reified, and whether it can be made non-reified?
https://github.com/Litote/kmongo/blob/a64be58cf52e42b60e057317ff7ff68d5429ea17/kmongo-coroutine-core/src/main/kotlin/org/litote/kmongo/coroutine/CoroutineCollection.kt#L1856
Concretely, maybe this line can be rewritten? If using
T::classcan be avoided, there's no need for the function to be reified, thus allowing it to be used in non-inline generic functions.https://github.com/Litote/kmongo/blob/a64be58cf52e42b60e057317ff7ff68d5429ea17/kmongo-coroutine-core/src/main/kotlin/org/litote/kmongo/coroutine/CoroutineCollection.kt#L1859
The
savefunction has, I believe, similar behavior if the involved class has an _id property, without it being reified.https://github.com/Litote/kmongo/blob/a64be58cf52e42b60e057317ff7ff68d5429ea17/kmongo-coroutine-core/src/main/kotlin/org/litote/kmongo/coroutine/CoroutineCollection.kt#L1262
My use case is as follows: we are building a internal library where we want to write a class that handles certain operations with a MongoDB database, but the concrete type can vary between different usages of the library. It is impossible to write this class using inline functions and reified generics, so we must use non-reified functions.