Sign in to track progress and bookmarks.
Pulling data from a list is O(N). Pulling from a Dictionary or Lookup is O(1). Choosing the right mapping structure is critical for performance.
Creates a 1:1 mapping. Every key MUST be unique. If ToDictionary encounters a duplicate key, it throws an ArgumentException. **Use Case:** Mapping User objects by their unique ID.
Creates a 1:Many mapping. It's essentially a Dictionary<TKey, IEnumerable<TElement>>. If multiple items share the same key, it groups them together into a collection. **Use Case:** Grouping Employees by their Department ID.
Unlike a Dictionary, a Lookup is immutable and **Null-Safe**. If you try to access a key that doesn't exist in a Lookup, it returns an empty sequence instead of throwing a 'KeyNotFoundException'. This makes your code much cleaner and less 'branchy'.
Q: "Should I call ToDictionary inside a loop?"
Architect Answer: "NO! This is a common performance killer. Create the Dictionary/Lookup **once** before the loop starts, and then do O(1) lookups inside. A 'ToDictionary' involves copying all data and calculating hashes—it's expensive."
Quizzes linked to this course—pass to earn certificates.
On this page
1. ToDictionary (Unique Keys) 2. ToLookup (One-to-Many) 3. Lookup Resilience 3. Architect Insight