Accidentally introducing unstable classes may silently introduce performance regressions in the Android compose library.
Proposed solution
It's possible to surface stability issues using the compose compiler reports. We could generate these reports in CI and simply check for any classes marked Unstable.
Problem
Accidentally introducing unstable classes may silently introduce performance regressions in the Android compose library.
Proposed solution
It's possible to surface stability issues using the compose compiler reports. We could generate these reports in CI and simply check for any classes marked
Unstable
.