tree 2389f8acd7e9fe76bd3bcc596fdf0a20e9bb64ec
parent 4fe809f80a259ff41a77ba0257e44802907ccb80
author Roman Elizarov <elizarov@gmail.com> 1605691541 +0300
committer GitHub <noreply@github.com> 1605691541 +0300
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJftOiVCRBK7hj4Ov3rIwAAdHIIAGr1QEX7bKQXJM3ZZmzglr4j
 QNiCJIN2Z88skzmTbeplMC7QKz6tglPBXatECdKWh84M96+1e02P5jq6K57T7+0j
 jHSk6c9KOHPZ7f8Rp2T4zmLXDf/KzpcxoYzGNwTK/tGph6c7tBH73T9Bfl75uksI
 VlSdCFfj0mywJd04jd8WO30DfKj4QenSjTad/Ji7ONNgpauFhEytVZkg2hEd9l1q
 DmgU5+cmIZASDQGu20aWGAaU20b0e8z79OqX1gCMTJ2ZlrcaulBShI6fyOqea18J
 IsEY5c58nJnaC0m1Szoy7RfHNRP3NAVwwQsCMrThNhdtBqpncnNBTXDYwEAHm+I=
 =ACzv
 -----END PGP SIGNATURE-----
 

Clarify thread-safety of SharedFlow methods in docs (#2399)

* Clarify thread-safety of SharedFlow methods in docs

* Override MutableSharedFlow.emit to attach a more appropriate docs than the one inherited from FlowCollector.
* Clarify thread-safety of all the MutableSharedFlow & MutableState "mutating" methods.

The latter is needed, because Flows, in general, are sequential, but shared flows provide all the necessarily synchronization themselves, so, to avoid confusion it makes sense to additionally mention thread-safety of shared flows in all the relevant mutating functions.