How do generic constraints and variance make a C# API safer, and how would you explain covariance versus contravariance?

Generic constraints, covariance, and contravariance

Uses constraints to express required operations and explains safe assignment direction for generic producers and consumers.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Constraints state what a type argument must support, such as class, struct, notnull, a base type, an interface, or a public parameterless constructor. They let generic code call those guaranteed members without reflection or runtime guessing. Covariance with out allows a producer such as IEnumerable<string> to be used as IEnumerable<object>. Contravariance with in allows a consumer such as IComparer<object> to be used where an IComparer<string> is needed. A generic type is invariant unless its declaration safely permits one of those directions.

Full answer below

Practice focus

Generic constraints, compile-time capabilities, covariance, contravariance, invariance, reference-type restrictions, and API design.

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
Generics become valuable when their type relationships communicate what an API can safely do. Constraints and variance solve different problems: available operations versus assignment compatibility.
Constraints state what a type argument must support, such as class, struct, notnull, a base type, an interface, or a public parameterless constructor. They let generic code call those guaranteed members without reflection or runtime guessing. Covariance with out allows a producer such as IEnumerable<string> to be used as IEnumerable<object>. Contravariance with in allows a consumer such as IComparer<object> to be used where an is needed. A generic type is invariant unless its declaration safely permits one of those directions.

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

Using covariance to justify adding a different subtype to a mutable collection.
Confusing the in parameter modifier with generic contravariance.
Adding a new() constraint only to construct dependencies inside domain logic.
Using object and repeated casts when a small interface constraint expresses the contract.

How do generic constraints and variance make a C# API safer, and how would you explain covariance versus contravariance?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section

Skill areas

Suggest an improvement