Fixed
Status Update
Comments
be...@google.com <be...@google.com>
al...@google.com <al...@google.com> #2
Triage notes: Likely still an issue, but keeping at P3.
al...@google.com <al...@google.com> #3
(less of an issue with strong skipping enabled)
al...@google.com <al...@google.com> #4
Triage notes: Raising to P2
, pulling back into the Inbox to get assigned.
Description
Jetpack Compose version: compose-bom:2023.05.01 → 1.4.3
Jetpack Compose Compiler version: 1.4.7
Jetpack Compose components used: ui, ui-graphics, ui-tooling-preview, material3, ui-tooling
Android Studio Build: Android Studio Flamingo | 2022.2.1 RC 1
Kotlin version: 1.8.21
I was experimenting with the Compose compiler reports and wanted to identify which classes are inferred as stable. In most cases, everything seemed fine, but I noticed a potential issue when a class extends an unstable class. The Compose compiler incorrectly considers it as stable, which I believe might be a bug (please correct me if I'm mistaken). Let's consider the following code as an example:
When I enable the Compose compiler reports and invoke it, the classes.txt file displays the following output:
The Parent class is correctly inferred as unstable, but the Child class is incorrectly inferred as stable. Shouldn't this be considered a bug? Additionally, the compiler reports suggest that something like this is skippable, which I believe should not be the case.