A modern programming language that makes developers happier.

kotlinlang

If I have a `MutableState`, I can expose it as *read-only* value to other classes as `State&lt;String&gt;`, just like:
```private val _title = mutableStateOf("abc")
val title: State&lt;String&gt; = _title```
Is there a way to do this with `SnapshotStateList&lt;&gt;` too? How would I do this for example with:
```private val _titles = mutableStateListOf&lt;String&gt;(...)
val titles: ??? = _titles```

```val titles: List&lt;String&gt;
    get() = _titles```

Also the `MutableState` case can be simplified to:
```var title by mutableStateOf("abc")
    private set```

Thanks <@U01JTGH1UMD>! Tho, if a composable would use this titles variable, would it be recomposed when _titles changes? Since it's not aware of a State object, but just a List&lt;String&gt;. Or is compose smart enough for that?

Yep. Indirect read of the state will also work.

Is this a common pattern? I remember following this backing property pattern for live data but I haven't done it with compose and it seems to be no worse off.

<@UN85K2RQR> i think the way <@U01JTGH1UMD> wrote it is the way you should do it (with private set) for basic states

It depends on when you want the read to happen. `State&lt;T&gt;` allows consumers to obtain the state holder without performing a read, while `var ... by mutableStateOf(...)` forces a read when the field is accessed.