perf(mangler): use combined exclusion set for name generation

[camc314]

Build a single FxHashSet containing all excluded names (unresolved references, keep_name_names, and conditionally root_bindings) instead of doing 3-5 separate hash lookups per candidate name in the generation loop.

[camc314]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• perf(mangler): use combined exclusion set for name generation #17381 👈 (View in Graphite)
• perf(mangler): optimize slot assignment with pre-computed ancestor sets #17379 : 1 other dependent PR (#17382 )
• feat(allocator/bitset): add clear method to reset all bits #17380
• perf(mangler): avoid ToString allocations #17378
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codspeed-hq]

CodSpeed Performance Report

Merging #17381 will degrade performance by 15.1%

_{Comparing c/12-26-perf_mangler_use_combined_exclusion_set_for_name_generation (fbd84ef) with c/12-26-perf_mangler_optimize_slot_assignment_with_pre-computed_ancestor_sets (4044df2)}

Summary

❌ 3 regressions
✅ 35 untouched
⏩ 7 skipped¹

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	mangler[cal.com.tsx]	2.8 ms	3.2 ms	-12.25%
❌	Simulation	mangler[binder.ts]	717.7 µs	761.1 µs	-5.7%
❌	Simulation	mangler[RadixUIAdoptionSection.jsx]	12.9 µs	15.2 µs	-15.1%

Footnotes

1. 7 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩