A set comprehension uses curly braces and produces a set, dropping duplicates as it goes. This is the cleanest way to compute 'how many distinct lengths', 'unique first letters', or 'normalised forms' from a list. The output is unordered; sort it before printing or comparing if order matters in your test. Time complexity is O(n) for n inputs because each insertion into a set is amortised O(1).

When you only need the unique projections (the IDs, the roles, the dates), a set comprehension is the right tool. When you need the unique objects themselves, a set comprehension cannot help directly because dicts are not hashable. The sentinel pattern (seen set plus an explicit loop) is the canonical alternative and runs in O(n) with O(n) extra space. Hashable replacement values (a tuple of fields, a frozenset of items) can sidestep the loop, but the explicit pattern is usually clearer.

Intersection, difference, and union can all be expressed as set comprehensions, but the operator forms (&, -, |) are shorter, idiomatic, and dispatched to the underlying C implementation, so they are also faster. Reach for the comprehension form only when the predicate is more complex than 'is in the other set' (case-insensitive comparison, normalised match). The same operators also work with frozenset, which gives you immutable, hashable sets when you need to use them as dict keys.