Tag

#kotlin-coroutines

80 posts155 followers

Explore Hashnode

Alternatives

Why Your Flow Refuses to Hop Threads: Context Preservation, flowOn, and channelFlow in Kotlin

Why withContext breaks flow { } in Kotlin. Learn context preservation, when to use flowOn or channelFlow, and the Android failures that crash apps.

11 min readandroid-expert.hashnode.dev

Android ExpertNov 2

Dropped on the Floor: Conflation in Kotlin Flows and the UI Events You Never Saw

Learn how Kotlin Flow conflation drops events in StateFlow, SharedFlow, and collectLatest, and fix it with Channels, buffers, and tested patterns.

11 min readandroid-expert.hashnode.dev

Manuel Alejandro HermosoOct 13

An AI agent that asks before it pays: human approval for tool calls in Kotlin

Build a Kotlin AI agent that pauses before a tool call and waits for a person to approve it. The pause survives a restart, and the tests need no model

9 min readdeeptelar.hashnode.dev

Ganesh Rama HegdeFeb 23

Chapter 1 : UseCase01 - Coroutine Builders and Execution Semantics

Mental Model: What Is a Coroutine? A coroutine is a suspendable computation, represented as a state machine, executed under a Job, scheduled by a dispatcher and resumed via a continuation. It is not a

13 min readkotlindeepdive.hashnode.dev

Ganesh Rama HegdeFeb 21

Chapter 30 : UseCase27 - Flow Cancellation & Cooperative Cancellation

Flow cancellation is not an optional feature. It is a core part of how coroutines are designed to behave. When a collector stops collecting, the entire upstream flow is cancelled automatically. This i

6 min readkotlinflow.hashnode.dev

Ganesh Rama HegdeFeb 20

Chapter 27 : UseCase24 - StateFlow (State Holder Semantics)

What is StateFlow? StateFlow is a special type of SharedFlow that: Always holds a current value Requires an initial value Replays the latest value to new collectors Conflates updates automatically

3 min readkotlinflow.hashnode.dev

Ganesh Rama HegdeFeb 20

Chapter 28 : UseCase25 - Hot vs Cold Flow comparison

In this use case we will do an architectural level comparison of hot versus cold flow. CODE IMPLEMENTATION package org.kotlinflowlearner.stockflow.usecases.uc25 import kotlinx.coroutines.flow.* impor

4 min readkotlinflow.hashnode.dev

Ganesh Rama HegdeFeb 19

Chapter 26 : UseCase23 - SharedFlow (Hot Streams)

Everything that we have seen until now was cold flows. Now we enter the world of "hot” flows. Cold flow means: Nothing runs until collected Each collector gets its own independent execution Flow re

4 min readkotlinflow.hashnode.dev

Ganesh Rama HegdeFeb 19

Chapter 25 : UseCase22 - Context Switching with flowOn

In this chapter we answer the core question : If Flow is sequential, then how do we control which thread executes which part? That’s what flowOn does. Flow is context-preserving by default. It means t

2 min readkotlinflow.hashnode.dev

Ganesh Rama HegdeFeb 17

Chapter 23 : UseCase20 - Buffering for Performance

There are real-world cases where producer is faster than consumer. By default, Flow is sequential. That means: Upstream emits Downstream processes Only then next value emits This is slow but safe. But differing speeds of producers and consumers ...