chore(benchmark): enable cfg for linter benchmarks.

[rzvxa]

The benchmark result on this PR - if we filter out the unstable benchmarks - can also be used to show the total impact of CFG enable rules.

[graphite-app]

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

Add the label “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.

[rzvxa]

• feat(linter): add CFGLintContext for rules with #[use_cfg]. #3747
• perf(linter): only generate cfg when we have a rule which depends on it. #3745
• feat(linter): add use_cfg attribute. #3744
• chore(benchmark): enable cfg for linter benchmarks. #3746 👈
• main

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

Join @rzvxa and the rest of your teammates on Graphite

[codspeed-hq]

CodSpeed Performance Report

Merging #3746 will degrade performances by 5.87%

_{Comparing 06-18-chore_benchmark_enable_cfg_for_linter_benchmarks (49d28c0) with main (1b3cd6c)}

Summary

⚡ 1 improvements
❌ 1 regressions
✅ 20 untouched benchmarks

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

Benchmarks breakdown

	Benchmark	main	06-18-chore_benchmark_enable_cfg_for_linter_benchmarks	Change
❌	codegen_sourcemap[react.development.js]	2.1 ms	2.2 ms	-5.87%
⚡	transformer[RadixUIAdoptionSection.jsx]	281.6 µs	261.8 µs	+7.58%

[graphite-app]

Merge activity

• Jun 19, 1:12 AM EDT: The merge label 'merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Jun 19, 1:12 AM EDT: Boshen added this pull request to the Graphite merge queue.
• Jun 19, 1:17 AM EDT: Boshen merged this pull request with the Graphite merge queue.