Why not StateFlow instead of Value?

[YektaDev]

Hi.
I'm impressed by the idea behind this library and found it the best available approach to achieve multi-platform navigation, so thanks for the effort! I was trying to get started. While reading the documentation, I noticed the Value class:

Value - is a multiplatform way to expose streams of states. It contains the value property, which always returns the current state. It also provides ability to observe state changes via subscribe/unsubscribe methods. There is MutableValue which is a mutable variant of Value.

I'm wondering if there are some reasons for not using Kotlin's StateFlow in order to achieve this functionality?

[arkivanov]

Hello. This looks like a duplicate of #46.