I've deliberately avoided touching benchmarks.
Regarding collectIndexed -- the proposed implementation is not identical, capturing mutable ints will be boxed on each emission, while spilling it into the state of flow collector explicitly leaves it as int type

Looks like after this change, coroutines 1.6.0 isn't backward compatible, when Flow<T>.collect(action) used in library. Is it expected?
originally reported at rsocket/rsocket-kotlin#201

This change makes the documentation confusing in some places.

In SharedFlow.collect it says "To emit values from a shared flow into a specific collector ... collect { ... } extension should be used." but collect extension no longer exists.

In Flow.collect it says "To ensure the context preservation property, it is not recommended implementing this method directly. Instead, AbstractFlow can be used as the base type to properly ensure flow's properties." but every time a call to collect is made on any Flow we're anonymously implementing collect directly, usually with the SAM conversion.

@zjuhasz thanks for noticing, shared flow documentation is fixed in #3127

but every time a call to collect is made on any Flow we're anonymously implementing collect directly, usually with the SAM conversion.

Flow interface is not anonymously implemented during collect SAM-conversion, only FlowCollector is, which is perfectly safe