How do you choose between IEnumerable, IReadOnlyCollection, IReadOnlyList, set, and dictionary contracts in a public C# API?

Choose the narrowest useful collection contract

Chooses between sequence, counted, indexed, set, and dictionary contracts based on required operations and complexity.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I choose the interface from the operations the method actually requires. IEnumerable<T> represents a sequence and may be lazy or one-shot; it does not promise cheap counting, indexing, or repeatable enumeration. IReadOnlyCollection<T> adds a count, and IReadOnlyList<T> adds indexed access without promising that another owner cannot change the backing collection. IReadOnlySet<T> expresses uniqueness and membership, while IReadOnlyDictionary<TKey,TValue> expresses keyed lookup. I use mutable ISet<T> or IDictionary<TKey,TValue> only when mutation is intentionally part of the method's contract.

Full answer below

Practice focus

Collection contracts, operation guarantees, repeatability, ordering, indexing, uniqueness, keyed lookup, mutation ownership, complexity, and materialization.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
The type in a method signature tells callers which operations are reliable. Accepting or returning a broader abstraction than the behavior supports creates hidden enumeration and complexity assumptions.
I choose the interface from the operations the method actually requires. IEnumerable<T> represents a sequence and may be lazy or one-shot; it does not promise cheap counting, indexing, or repeatable enumeration. IReadOnlyCollection<T> adds a count, and IReadOnlyList<T> adds indexed access without promising that another owner cannot change the backing collection. IReadOnlySet<T> expresses uniqueness and membership, while IReadOnlyDictionary<TKey,TValue> expresses keyed lookup. I use mutable ISet<T> or IDictionary<TKey,TValue> only when mutation is intentionally part of the method's contract.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Accepting IEnumerable and then assuming Count and index access are cheap.
Returning a read-only interface while continuing to mutate the same backing list unexpectedly.
Using a list for repeated membership checks on large inputs without measuring complexity.
Choosing a dictionary without defining duplicate keys or key comparison rules.

How do you choose between IEnumerable, IReadOnlyCollection, IReadOnlyList, set, and dictionary contracts in a public C# API?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue practice

Go deeper

Tech stacks

Skill areas

Suggest an improvement