Determine if Two Strings Are Close

Start by clarifying the exact contract for Close Strings: input representation, mutation rules, duplicate behavior, and what should happen on invalid or empty input. The core idea is separating character-set equality from frequency multiset equality. Work a tiny example aloud and name the invariant after each step, because that is the proof that the approach stays correct as the input grows.

A dependable implementation plan is to reject unequal lengths; count frequencies; compare used character sets; sort nonzero frequency counts; compare multisets. Matching counts alone is insufficient when alphabets differ. Keep the code aligned with that invariant instead of adding special cases that silently change the contract. Test the smallest input, a normal case, duplicates or ties where relevant, an adversarial boundary, and a case that exercises the failure path. The expected complexity is O(n + A log A) time and O(A) space. Explain both time and auxiliary memory, including recursion or helper structures; do not hide sorting, copying, or repeated scans. If the title omits critical constraints, say what you need to know before committing to a more specialized solution.