Okay what if a library has a data class that's eli...
# announcements
k
Okay what if a library has a data class that's eligible to be inlined, and then a new version comes out that does something that breaks that, for example it adds a constructor with some logic. Normally code that was compiled would work with the new constructor, but with inline classes it would be ignored.
c
Why would that happen? I think that on upgrade that class would just not be inlined.
k
If you don't recompile the project itself and just swap in new dependency versions.
c
I see your point now. I'm working mostly with Android, didn't thought of that.
Is that a common practice though? Sounds like a very risky thing to do.
k
Probably not, but it's something that should work, and binary compatibility it's also one of the things listed under the backwards compatibility things Kotlin itself guarantees.