A modern programming language that makes developers happier.

kotlinlang

where can i see changes in the compose compiler?

I noticed stuff breaking going from 2.0.10 to 2.0.20 in my library without changing any library code

You can run `git log v2.0.20..v2.0.10 plugins/compose` on a clone of the repo

I don't think GItHub lets you filter to a range in a directory <https://github.com/JetBrains/kotlin/commits/master/plugins/compose>

We can cheat by using Android's mirror and Gitiles though <https://android.googlesource.com/platform/external/jetbrains/kotlin/+log/v2.0.20..v2.0.10/plugins/compose>

Strong skipping is enabled by default in 2.0.20, could it be that?

Thanks for the pointers <@U0BFDUP0E>. was looking for any sort of change log

But I just realized there is a section on the compiler on <https://kotlinlang.org/docs/whatsnew2020.html#compose-compiler|What's new in Kotlin 2.0.20>

<@U0306J7T4QP> i'll check when i can. not sure what strong skipping is and how it can affect behavior though

Basically previously unskippable composables become skippable and lambdas are remembered for you

<https://developer.android.com/develop/ui/compose/performance/stability/strongskipping>

ok that makes it a bit clearer. i can see how this might cause issues

btw, i disabled it and everything works like before even with the 2.0.20 compiler :ok_hand:

I'd love to know what broke for you though, do you have an example?

The <https://github.com/composablehorizons/compose-unstyled/blob/main/core/src/commonMain/kotlin/BottomSheet.kt|BottomSheet component> of my library breaks. When it is enabled even though the anchor points are calculated correctly (same values) the sheet does not 'rest' at the right places.

I don't have time to check right now, but it might be either the BottomSheet code itself (the file I already linked) or the old version of <https://github.com/composablehorizons/compose-unstyled/blob/main/core/src/commonMain/kotlin/androidx/compose/foundation/gestures/CoreAnchoredDraggable.kt|AnchoredDraggable> I copied from Compose in my library.

if you want to test it out yourself you can clone the repo and use the `demo-sheet` configuration on android. <https://github.com/composablehorizons/compose-unstyled/commit/5b9fc256331b17945b3b810da61b662712761071|add strong skipping> and try it out.

Do I miss something or do the docs don’t mention libraries? Does a library author need to recompile and publish a new version?

No, they don't have to. Composables in libraries would follow the rules of whatever they were compiled with, either with or without strong skipping mode

<@U0306J7T4QP> does this also mean that if my library does not enable strong skipping mode, an app consuming my library can still enable strong skipping mode without affecting the behavior of my lib?