Why SharedFlow never ends? Why doesn't SharedFlow propagate the completion event from the upstream flow?

Consider a flow like 
```kotlin 
flowOf(1).sharedIn(scope, start)
```
It seems reasonable that each subscriber could know that no more data will be coming.

I'm wondering about the design decision behind this behavior?