HighFile-scopeKotlin Plug & play

Wrap blocking operations with proper dispatchers

Run blocking I/O and CPU-intensive work inside withContext(Dispatchers.IO) or Dispatchers.Default respectively. Never block the main thread.

Why this matters

Misplaced blocking work causes ANRs, thread starvation, and throughput collapse.

Side-by-side examples engineers can pattern-match during review.

Avoid

suspend fun read(): String = File("/tmp/x").readText() // runs on caller context

Prefer

suspend fun read(): String = withContext(Dispatchers.IO) { File("/tmp/x").readText() }

Bad

runBlocking { heavyBlocking() } // on main

Good

withContext(Dispatchers.IO) { heavyBlocking() }

From the same buckets as this rule.

Critical
Avoid Blocking Calls to Async Methods
Blocking async methods with `.Result` or `.Wait()` can cause deadlocks and prevent efficient asynchronous execution. Use `await` instead for proper async behavior.
concurrency-safetyperformance-efficiency
Critical
Do Not Call `wait()` When Holding Multiple Locks
Ensure that `wait()` is not called while holding multiple locks to prevent deadlocks.
concurrency-safety
High
Avoid Using Mutable Global Variables
Identify global variables that are mutable (e.g., lists, dictionaries). Global mutable state can cause unpredictable behavior. Recommend using local variables or encapsulating state in a class.
concurrency-safetymaintainability+1