liveBook · Manning

Implicit output

An implicit output is an observable effect of a computation, such as changing external state or raising an exception, not represented by its return value.

How 2 Manning books explain it

Grokking Simplicity

An effect of a function that changes external state or performs an observable operation rather than returning the result directly.

How it is used
Uses implicit outputs to identify hidden coupling in actions and guide refactoring toward explicit return values.
How deep it goes
Explains definitions, testing consequences, copy-on-write extraction, and asynchronous callbacks, but does not develop implementation details beyond JavaScript examples.
Examples
Uses shopping-cart mutation, cart-total calculation, DOM updates, shipping icons, and asynchronous cost and shipping calculations.
What you can do after
Diagnose/debug with it by locating hidden outputs, then replace them with return values or callbacks to improve testing and reuse.

Read how Grokking Simplicity explains implicit output →

Unit Testing Principles, Practices, and Patterns

A hidden output is an effect of a computation, such as a side effect or exception, that is not represented by its return value.

How it is used
Explains why side effects complicate functional reasoning and testing.
How deep it goes
Defines hidden outputs, identifies them through referential transparency, and contrasts them with explicit method outputs.
Examples
Uses Increment, AddComment, CalculateDiscount, side effects, and exceptions as concrete comparisons.
What you can do after
Diagnose hidden behavior by comparing a method call with its return value and inspecting state changes or exceptions.

Read how Unit Testing Principles, Practices, and Patterns explains implicit output →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.