Uli Bubenheimer

Another element to consider here: MapsInitializer may need to be a part of an app's map initialization pipeline: the `GoogleMap()` subcomposition composition phase should not be delayed until after MapsInitializer...

@wangela Just FYI: the 4.3.3 release says that it fixes this issue, but that is not the case. I think this mixup happened because I mentioned this issue in one...

@wangela That link says it "closes" #501

I've added two related issues on the Google issue tracker: https://issuetracker.google.com/issues/340494390 https://issuetracker.google.com/issues/340476594

Another consequence: updating padding and camera position together is not possible - camera will always be set instantly, then eventually padding when applying composition. This means that the camera will...

@asos-luisalcantara your modifications make more sense to me than what's in the release. Wonder what might happen if you disable reuse entirely? (Not performant enough, I guess, but does it...

@asos-luisalcantara @oceanjules The main problem I see with the current implementation here is `onReset = {}`. This will trigger reuse in a ReusableComposition, but the surrounding code does not support...

@oceanjules using non-null `onReset` means that a `View` instance previously created by `factory` will (or may) be reused when the `AndroidView` component usage occurs within a `ReusableComposition`, when the composition...

I'm pretty sure that I do not want to mark all my completely safe usages of `invokeOnCompletion()` with `@DelicateCoroutinesApi`. It's no more delicate than many other everyday coroutines concepts. I...

> > I have seen @DelicateCoroutinesApi being overused for other APIs already. > If you feel that you are proficient in kotlinx.coroutines, please use a global opt-in: I don't think...