perf(linter, ast-tools, coverage): Use FxHashSet instead of std::collections::HashSet

[camchenry]

No description provided.

[camchenry]

• perf(linter, ast-tools, coverage): Use FxHashSet instead of std::collections::HashSet #6001 👈
• chore(oxc): ban std::collections::HashMap in favor of FxHashMap #5996
• perf(ast-tools): use FxHashMap over std::collections::HashMap #5997
• perf(linter, prettier, diagnostics): use FxHashMap instead of std::collections::HashMap #5993
• main

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

Join @camchenry and the rest of your teammates on Graphite

[graphite-app]

Your org has enabled the Graphite merge queue for merging into main

Add the label “0-merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix.

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

[codspeed-hq]

CodSpeed Performance Report

Merging #6001 will not alter performance

_{Comparing 09-23-perf_linter_ast-tools_coverage_use_fxhashset_instead_of_std_collections_hashset_ (0ab41b9) with 09-23-perf_ban_std_collections_hashmap_in_favor_of_fxhashmap_ (e14e488)}

Summary

✅ 29 untouched benchmarks

[camchenry]

I think the snapshot changes are because my editor automatically stripped some whitespace from some lines. I can revert if desired, but at least this way it won't be able to happen again in the future.

[overlookmotel]

Nice!

[graphite-app]

Merge activity

• Sep 24, 4:41 AM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Sep 24, 4:42 AM EDT: Graphite disabled "merge when ready" on this PR due to: a merge conflict with the target branch; resolve the conflict and try again..
• Sep 24, 4:42 AM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.