CLOJURE / CORE CONCEPTS
Numbers, keywords, symbols, and nil
Learn how numbers, keywords, symbols, and nil works in Clojure, why the underlying model matters, and how to apply it in a small program without hiding important trade-offs.
What you will learn
- Explain numbers in Clojure using the correct mental model
- Trace a focused Clojure example and predict its result before execution
- Recognize a boundary case involving keywords and handle it deliberately
Understanding Numbers, keywords, symbols, and nil
Numbers, keywords, symbols, and nil belongs to the practical core of Clojure. Start by identifying the values or state involved and the rule that connects the input to the result.
Trace the example one operation at a time. Keep numbers visible in the code rather than hiding it behind an abstraction before the behavior is understood.
Test a normal case and a boundary case. The difference between the prediction and the observed result is the most useful signal for deciding what to review next.
Numbers, keywords, symbols, and nil is a defining part of practical Clojure work. Start by identifying the data or state involved, then trace the operation that changes or interprets it. Pay attention to the rules Clojure applies at this boundary, because those rules explain both the useful behavior and the common failure modes. This lesson keeps the example deliberately small, then connects it to functions, threading macros, and equality so the ideas form a coherent progression rather than a list of isolated syntax facts.
Worked examples
Numbers, keywords, symbols, and nil example
A focused Clojure example for numbers.
(def message "Hello from Clojure")
(println message)
// Lesson 4: numbers. Change one value and predict the result before running it.Example explained
Line 1Identify where numbers appears in the Clojure example and name the data it operates on.
Line 2Trace the relevant Clojure rule one operation at a time, recording any state, type, or control-flow change.
Line 3Change one input or boundary condition, predict the result, and compare that prediction with the documented outcome.
Important notes
Keep the first numbers example small enough to trace completely.
Use the normal Clojure toolchain or browser workspace to compare the actual result with your prediction.
Common mistakes
Treating numbers as punctuation to memorize instead of a Clojure behavior to reason about.
Ignoring keywords until it appears in production data or a larger program.
Try it yourself
Change, predict, then run
Create a small Clojure example that demonstrates numbers. Add a normal case and a boundary case, write down the expected result for each, then explain which Clojure rule produces that result. Lesson 4 should remain small enough to trace without guessing.
Open Clojure workspaceCheck your understanding
What is the best first step when working with numbers?
- Identify the data and predict the result
- Add more abstraction immediately
- Ignore boundary cases
- Memorize punctuation only
Show answer
A clear input, operation, and predicted result create a testable mental model.