Here's a new article covering inline classes, their inner workings and some use cases https://kotlinexpertise.com/kotlin-inline-classes/

nice article - we've ran into a few issues when trying to use

inline class

• no

init

means you cant can't constrain them on construction (like a

PositiveInt

class where the constructor checks the provided value) • mocking frameworks dont play nice them. if you have a function that takes

fun myFun(positveInt: Int)

and you stub it using something like mockito, then switching it to

fun myFun(positveInt: PositiveInt)

, it is tough to wrangle mockito matchers and verifiers to do what you want them to do

Thank you - have you tried mockk already?

have not tried it with mockk yet, but saw (https://github.com/mockk/mockk/issues/152) which looks like it might have some workarounds we could use https://youtrack.jetbrains.com/issue/KT-28055 is for the input constraints which would be nice for us

I haven’t run into related issues yet but definitely appreciate your heads up!

I am showing ViewModels in a RecyclerView, is it a good usecase to use inline classes with the ViewModel as parameter, and an interface with the method getLayouResId() for specifying the layout resource id? So that the RecyclerViewAdapter automatically can bind the viewmodel with layout to a viewholder?