Hi guys, great to see alpha04 bringing performance optimizations to

LazyColumnFor

! I'm not sure if I'm doing something wrong, but I can't see any difference with the issue I filed sometime ago. I only had to change the version number for Kotlin and compose from alpha01 (last one I tested with) to 04. I also did Rebuild project a few times, not sure if this is enough for changes to take effect. Also, what I see is that on every scroll the compose function gets called for certain items (added a

Log.w

inside it to verify). On the other hand, everything is really smooth with

RecyclerView

and with a more complex view than the one in the sample project in the issue. I haven't changed anything to the code, apart from versions, in the sample project in the bug, probably I need to add something? Appologies if this is configuration issue! Thanks!

Hi! We only merged one from the planned optimizations. Probably exactly your use case is not yet affected. Please expect more optimizations to come in the next releases. Are you saying that with a list like from this bug: https://gist.github.com/Rokata9/856bc5cdd25aa187a9e6783c747401b1 you are getting items recomposed on every scroll on alpha04? If yes, could you please comment on a bug with a bit more details(for example please share how your Wallpost class is defined). Thanks!

Hi Andrey, sorry I'm replying that late, I commented on the bug here, I suggest we keep the discussion there. 🙂