Ambients - why sometimes ambients are "registered" with the value directly and sometimes you pass a remembered state of the value? What's is the logic/meaning behind this? I thought that there is already a logic in ambient how to compare new provided value to the previous.

do you have an example?

ConfigurationAmbient - it is a remembered state vs. ContextAmbient - context is passed directly.

ah. `ConfigurationAmbient`'s wireup to get changed values is a bit different in the implementation details and could probably be simplified a bit. It's remembering an observable state holder so that the

Providers

call recomposes when it changes via the callback.

So when the provided value for ambient is not remembered state, recomposition ambient value can be caused done only by new Providers() call?

A new Providers call is the only way an ambient value can change

For Configuration, recomposition based on reading the MutableState holder is causing a new Providers call

Aha moment, obvious now! Thanks a lot.