-
Notifications
You must be signed in to change notification settings - Fork 175
Performance penalty throughout API from LatLng usages #152
Copy link
Copy link
Closed
Labels
externalThis issue is blocked on a bug with the actual product.This issue is blocked on a bug with the actual product.priority: p3Desirable enhancement or fix. May not be included in next release.Desirable enhancement or fix. May not be included in next release.releasedtype: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Metadata
Metadata
Assignees
Labels
externalThis issue is blocked on a bug with the actual product.This issue is blocked on a bug with the actual product.priority: p3Desirable enhancement or fix. May not be included in next release.Desirable enhancement or fix. May not be included in next release.releasedtype: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Type
Fields
Give feedbackNo fields configured for issues without a type.
android-maps-compose 2.2.1
compose 1.2.0-rc01
The android-maps-compose API imposes a performance penalty throughout by leveraging the Maps SDK LatLng type, which the compiler is currently unable to infer as stable. (Observed via compose compiler metrics: https://github.com/androidx/androidx/blob/androidx-main/compose/compiler/design/compiler-metrics.md)
I see 2 potential solutions:
I'd consider the second solution preferable.
Code example
In this example the Compose compiler deems
latLngunstable, rendering the composable function non-skippable.