chore(oxc): ban std::collections::HashMap in favor of FxHashMap

[camchenry]

No description provided.

[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.

[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

[codspeed-hq]

CodSpeed Performance Report

Merging #5996 will not alter performance

_{Comparing 09-23-perf_ban_std_collections_hashmap_in_favor_of_fxhashmap_ (f14ef7c) with main (c8682e9)}

Summary

✅ 29 untouched benchmarks

[graphite-app]

Merge activity

• Sep 24, 1:08 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, 1:08 AM EDT: Boshen added this pull request to the Graphite merge queue.
• Sep 24, 1:13 AM EDT: The Graphite merge queue couldn't merge this PR because it failed for an unknown reason (All comments must be resolved before merging).

[Boshen]

Where's the unresolved conversation?