kotlin-concurrency-and-flow

Kotlin concurrency and Flow

Core principle

Give asynchronous work an explicit owner and lifetime, then model durable state and transient events with primitives whose delivery and replay semantics match the product contract.

Procedure

1. Identify each coroutine owner, cancellation boundary, producer, consumer,

durable state, and transient event.

1. Before changing an API, compare its existing caller-visible contract with

the required owner and lifetime. If a suspend API already gives its caller cancellation, result, and failure ownership, finish with no change; do not add a scope, launch, callback, or deferred wrapper merely for convenience.

1. Select a scope whose lifecycle owns the work; do not retain arbitrary scopes

or hide unstructured launches behind non-suspending APIs.

1. Model renderable, current data as state and imperative one-shot work as an

event only when its loss and replay behavior are explicitly acceptable. Ask whether one consumer handles each event or every active consumer must receive it. A Channel hands each event to one consumer; a configured SharedFlow broadcasts to active consumers. If that consumer contract is unknown, state both options and the decision needed before choosing one. For a one-consumer navigation handoff that must survive a collector gap, choose a bounded Channel(Channel.BUFFERED) (not UNLIMITED) exposed as receiveAsFlow(); do not preserve a replay-zero SharedFlow after identifying event loss as the defect.

1. Choose Flow sharing and buffering semantics from the producer and consumer

lifetimes rather than from a default.

1. Read the focused reference for the material concern below.
2. Finish when cancellation, restart, replay, and failure behavior are all

observable from the public API and no caller must guess who owns the work.

Topic router