List Comparison & Set Operations

The four questions a list comparison answers

Comparing two lists is set arithmetic wearing plain clothes. Whatever the task is called in the office, it resolves to one of five operations, and the default view runs four of them at once so you do not have to decide up front which one you needed.

The settings that change the answer

• Case sensitivity is off by default, so Alice and alice count as one item. Turn it on for identifiers, tokens and paths on a case-sensitive filesystem, where the difference is real.
• Whitespace is trimmed by default. A trailing space is the single most common reason two lists that look identical share nothing at all: it survives a copy out of a spreadsheet cell and it is invisible on screen.
• Repeats inside one list are collapsed in the results but counted separately in the summary, so you can see that the first list had 412 rows and 398 distinct values without leaving the page.
• Sorting applies to the output only, using a numeric-aware comparison, so item2 lands before item10 instead of after it.
• Blank lines are dropped, which means a trailing newline at the end of a paste does not turn into an empty item that matches nothing.

What people actually use it for

• Reconciling two exports: who is in the CRM but not on the mailing list, or which SKUs the supplier sent that the catalogue has never heard of.
• Seeing what a change touched: two lists of config keys, environment variables or file paths, before and after.
• Skipping work already done: put the processed identifiers in the second list and take only in the first.
• Measuring overlap before merging two audiences, tag sets or keyword lists, where the intersection count is the answer on its own.

If the input is messy, remove duplicate lines and sort each list first so the output is easier to read. And if you are comparing two versions of the same text rather than two sets of items, use the diff checker instead: a diff cares about order and position, and a set comparison deliberately does not.