Uli Bubenheimer

> That's fair. If you think that some `DelicateCoroutinesApi`-marked API entry that is _often_, not just occasionally, the best tool for the job, then please open an issue for marking...

@realityexpander there is a regression introduced in android-maps-compose 1.4.21 that causes recomposed GoogleMap listeners to not be used. Wonder if this might contribute to your obstacles. #466

The delay in setting initial CameraPosition was first introduced in 2237950. Up until then setting the camera was prompt. I see now that this problem is not just about the...

@mishackee the concern I brought up in this issue is of a more theoretical and architectural nature, I have not quantified it. Reusing GoogleMap() inside a lazy list is optimized...

@mishackee thank you for adding this valuable detail. It is the type of behavior I would expect to see with this issue. However, a jump like that could also be...

This concern could be addressed by making the property non-public or whatever "internal" library consumers actually need.

~~Also, this property, in its present form, prevents performing initial composition of the `GoogleMap()` subcomposition in parallel with `GoogleMap` object initialization: #501~~ Edit: I don't think this is the case,...

To give an idea what my request flow code looks like: ``` repeatingTimerFlow .onCompletion { println("I rarely see this: $it") } .map { /* something */ } .onStart { withContext(Dispatchers.IO)...

Can a server delay ClientCall.Listener.onReady() to influence this behavior? Is onReady() only triggered in response to manual or automatic flow control on the server requesting data from the client? In...

After playing around with it a bit it seems to me that a request() call on the server is not what initially enables onReady()/isReady on the client.