Hello devs which one do you think it s better to be used and

Question

Hello devs which one do you think it s better to be used and why 1 private val stateData = MutableStateFlow lt State gt State Idle val state StateFlow lt State gt get = stateData Or 2 private val stateData = MutableStateFlow lt State gt State Idle val state StateFlow lt State gt = stateData

Lukas Sztefek · Answer

It s just about you convention and personal taste I prefer ```private val stateData = MutableStateFlow State Idle val state StateFlow lt State gt = stateData asStateFlow ``` The only reason I don t like syntax of getters and setters in kotlin

Javier · Answer

asStateFlow doesn t let you cast to MutableStateFlow I think so it is even better

FunkyMuse · Answer

That s a sweet solution too i was wondering whether the getter has a performance impact rather than a plain val

Lukas Sztefek · Answer

I doubt it

Javier · Answer

it should crash but I didn t try it personally

FunkyMuse · Answer

It won t crash I ve tried both solutions i wrote above I m just wondering if the getter is slower due to it not holding the data once the mutable one is created but only when it s called and whether this imposes a space complexity since the val of immutable state flow is immediately created after the mutable state flow

Javier · Answer

I am not talking about get or assignment

Javier · Answer

I am taking about using asStateFlow or not

Javier · Answer

and trying to recast it to MutableStateFlow

FunkyMuse · Answer

You re not casting it to MutableStateFlow You re exposing it as immutable StateFlow

Javier · Answer

yeah I know

Javier · Answer

but if someone is mad can try to cast it as MutableStateFlow

Javier · Answer

sample ``` ViewModel private val state = MutableStateOf val state StateFlow lt gt = state Fragment viewModel state as MutableStateFlow value = ```

FunkyMuse · Answer

Oh well that s a mistake right there hah I don t think this should be a matter of discussion Don t get me wrong I m trying not to stir this discussion aside

Javier · Answer

Someone said me that using `asStateFlow` you can t do that because it should crash But I have never tried that casting personally with our without `asStateFlow`

Javier · Answer

It should because it can be an additional argument to use `asStateFlow` instead of the other one

Ruckus · Answer

< FunkyMuse> As an unrelated note it s considered bad form to someone for a generic question like this that can be answered by anyone There s no reason to expect Roman to personally answer your questions You should probably refrain from doing it in the future unless you really do need to specifically address that person