Question: Why would this be preferred ```private val _myFlow = MutableStateFlow<String>("") va...

# coroutines

[streetsofboston]

Question:
Why would this be preferred

private val _myFlow = MutableStateFlow<String>("")
val myFlow: SharedFlow<String> = _myFlow.asStateFlow()

over

private val _myFlow = MutableStateFlow<String>("")
val myFlow: SharedFlow<String> = _myFlow

?
A MutableStateFlow is a StateFlow; why the extra call to asStateFlow()?

[Charlie Christensen]

I'm not 100% sure but I think this makes sure it can't be casted into a MutableStateFlow by the consumer

[louiscad]

Yes, that's what it does.

[streetsofboston]

Why would a consumer try to unsafely downcast it back to a MutableStateFlow...? Isn't that asking for problems. Consumers should just consume it, not try to find a way to write/update it.

[Charlie Christensen]

Yeah if you are responsible this isn't really an issue. This is just to guard against anyone who tries to do that

[Alex Prince]

yea exactly, it's just defensive programming, so that somebody down the line doesn't mess it up (probably you, if my experience is anything to go by)