A modern programming language that makes developers happier.

kotlinlang

I'm curious why compose keeps using the old `inline class` syntax and suppressing the deprecated warning as shown <https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/ui/ui-geometry/src/commonMain/kotlin/androidx/compose/ui/geometry/Size.kt;drc=e238bad05f051639c06b8a1df67d1c1eb0fa917b;l=40|here> instead of replacing it with `value class` after supporting Kotlin 1.5? I tried using value classes (with snapshot version of compose) in my app and there seems no problem.

There is an issue with some of our other tooling using value class that we were discussing how to move forward with. <@U6158UG1Z> has further details, I think it was around our binary compatibility tracking with the metalava tool but I might be remembering something else instead

<@UJBKXD0HH> You're remembering correctly.  I don't know how you manage to keep the current state of everything in your head :innocent:.  At first glance, it wasn't even until I read your response that I was able to remember why, even though I'm pretty sure I was the person who told you about that issue in the first place.

Yes, details here: <https://issuetracker.google.com/issues/189196253>