C# / DATA AND COMPOSITION
Collections, spans, and immutable data
Learn how collections, spans, and immutable data works in C#, why the underlying model matters, and how to apply it in a small program without hiding important trade-offs.
What you will learn
- Explain collections in C# using the correct mental model
- Trace a focused C# example and predict its result before execution
- Recognize a boundary case involving spans and handle it deliberately
Understanding Collections, spans, and immutable data
Collections, spans, and immutable data belongs to the practical core of C#. 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 collections 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.
Collections, spans, and immutable data is a defining part of practical C# work. Start by identifying the data or state involved, then trace the operation that changes or interprets it. Pay attention to the rules C# 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 strings, interpolation, and regular expressions so the ideas form a coherent progression rather than a list of isolated syntax facts.
Worked examples
Collections, spans, and immutable data example
A focused C# example for collections.
using System;
Console.WriteLine("Hello from C#");
// Lesson 9: collections. Change one value and predict the result before running it.Example explained
Line 1Identify where collections appears in the C# example and name the data it operates on.
Line 2Trace the relevant C# 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 collections example small enough to trace completely.
Use the normal C# toolchain or browser workspace to compare the actual result with your prediction.
Common mistakes
Treating collections as punctuation to memorize instead of a C# behavior to reason about.
Ignoring spans until it appears in production data or a larger program.
Try it yourself
Change, predict, then run
Create a small C# example that demonstrates collections. Add a normal case and a boundary case, write down the expected result for each, then explain which C# rule produces that result. Lesson 9 should remain small enough to trace without guessing.
Open C# workspaceCheck your understanding
What is the best first step when working with collections?
- 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.