Nesting depth

What it means

Nesting depth measures how deeply conditions, loops, callbacks, or blocks are enclosed. Deep nesting can make the main path difficult to see and increase the effort needed to reason about exits and error handling. Tools must state whether lambdas, callbacks, and language-specific constructs count.

Example

A function checks permissions, then loops through items, then handles retries inside a conditional. Guard clauses and extracted operations can expose the happy path without changing behavior.

Limitations

Shallow nesting is not automatically clearer if it spreads logic across obscure helpers. Some domain algorithms naturally require structured nesting. Review names, invariants, and tests with the depth signal.

How to use the signal

Check whether guard clauses preserve the domain sequence, since flattening control flow can merely move complexity into helpers.

Weave can associate deep-nesting changes with review comments and later fixes. Keep the threshold local to the language and team style, and use the result to select code for human inspection.