Functions as First-Class Citizens

In Clojure, functions are not special “things you can only call”. They are values you can pass around like any other value: put them in maps, return them from functions, and build behavior by composition.

This is one of the biggest practical shifts from Java, where functions historically lived behind methods and interfaces.

Why it matters in real code

• You build pipelines by assembling small functions.
• You avoid deep inheritance trees by composing behavior.
• You make “what varies” explicit by passing a function in.

Java mental model: similar to Java’s Function<T,R> and lambdas, but built into the language (no extra ceremony).

Once “functions are values” feels normal, higher-order functions stop looking magical and start looking like the simplest way to write clear data transformations.

In this section

• What It Means for Functions To Be First-Class in Clojure
  Understand what it means for functions to be values in Clojure, why that matters for Java developers, and how it leads directly to higher-order programming.
• Why First-Class Functions Matter in Real Clojure Code
  See how first-class functions improve reuse, testing, and API design for Java teams moving toward idiomatic Clojure.