liveBook · Manning

Implicit argument

An implicit argument is a function input supplied through context or language conventions rather than explicitly provided at the call site.

How 3 Manning books explain it

Grokking Simplicity

A code smell in which a function's name encodes a value that would more appropriately be supplied explicitly as an argument.

How it is used
Detects duplication when function names encode varying fields or operations instead of exposing them as values.
How deep it goes
Explains recognition, four refactoring steps, validation, nested updates, and callbacks, but stops short of a full language-internals treatment.
Examples
Uses shopping-cart field setters, quantity and size incrementers, multiplication functions, and nested shirt options.
What you can do after
Diagnose/debug with it by spotting name-encoded differences and refactoring them into explicit, validated arguments.

Read how Grokking Simplicity explains implicit argument →

Akka in Action, Second Edition

An implicit argument is a Scala method argument that the compiler can automatically supply from a compatible implicit value.

How it is used
Supplies Akka ask-operation parameters automatically, reducing repeated timeout arguments in asynchronous manager-worker workflows.
How deep it goes
Defines compiler lookup and demonstrates timeout insertion, but defers Scala’s broader implicit-scope rules.
Examples
Uses a manager parsing text through workers, with a three-second timeout and success-or-failure reports.
What you can do after
Apply it via Akka’s ask API by declaring a compatible implicit timeout and omitting that parameter from calls.

Read how Akka in Action, Second Edition explains implicit argument →

Type-Driven Development with Idris

An Idris function argument whose value is inferred from context rather than supplied explicitly, but remains available inside the function definition.

How it is used
Avoids spelling out type and length details that Idris can infer while retaining them in function types.
How deep it goes
Works through inference, explicit binding, pattern matching, and runtime erasure; does not develop formal inference rules.
Examples
Uses vector append, vector length, and createEmpties to demonstrate inference, named values, and pattern matching.
What you can do after
Apply implicit arguments to write vector functions, specialize them with named values, and pattern-match on inferred indices.

Read how Type-Driven Development with Idris explains implicit argument →

Related concepts

Questions about implicit argument

What is implicit argument?

An implicit argument is a function input supplied through context or language conventions rather than explicitly provided at the call site.

Which Manning books explain implicit argument?

Grokking Simplicity, Akka in Action, Second Edition and Type-Driven Development with Idris.

What kinds of implicit argument are there?

Kinds of implicit argument include auto implicit argument.

What is implicit argument a kind of?

Implicit argument is a kind of code smell. A code smell is a recognizable characteristic of source code that suggests a potential design, implementation, or maintainability problem, without necessarily indicating a functional defect.

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.