Fixed
Status Update
Comments
ry...@google.com <ry...@google.com>
as...@google.com <as...@google.com> #2
I simpler example would be appreciated. I tried to download the pull request and build it but it relies on, for example, `rustc` to be installed which I don't have installed on my compose development machine.
Does the program work without the compiler switch. That is, is `"-P", "plugin:androidx.compose.compiler.plugins.kotlin:experimentalStrongSkipping=true",` required to reproduce or is just changing the runtime enough?
Does the program work without the compiler switch. That is, is `"-P", "plugin:androidx.compose.compiler.plugins.kotlin:experimentalStrongSkipping=true",` required to reproduce or is just changing the runtime enough?
ap...@google.com <ap...@google.com> #3
Yeah, changing compiler switch(enable/disable StrongSkipping, enable/disable nonSkippingGroup) has no effect, only changing runtime make sense.
Sorry for that, I will try to extract an example when I'm free.
Sorry for that, I will try to extract an example when I'm free.
Description
I have created a code sample which shows the issue.
Steps to Reproduce:
Compile this code and start the TestKeyContent() composable. Observe the log messages.
Result:
The items list contains the elements 1...6 or only 2 (changes every 2 seconds). The element 2 is always part of the items. The composable KeyContent1 should log the message 'KeyContent1 remember 2' only in the composition phase. CORRECT! The composable KeyContent2 should also log the message 'KeyContent2 remember 2' only in the composition phase. BUG! Each recomposition creates a new log message 'KeyContent2 remember 2'.