Skip to content

refactor(various): update macros to use expr fragment specifier#11113

Merged
graphite-app[bot] merged 1 commit intomainfrom
05-18-refactor_various_update_macros_to_use_expr_fragment_specifier
May 18, 2025
Merged

refactor(various): update macros to use expr fragment specifier#11113
graphite-app[bot] merged 1 commit intomainfrom
05-18-refactor_various_update_macros_to_use_expr_fragment_specifier

Conversation

@overlookmotel
Copy link
Member

@overlookmotel overlookmotel commented May 18, 2025

Pure refactor. expr_2021 fragment specifier was I assume introduced in these macros by a codemod when we updated to Rust 2024 edition. None of these macros are used with input where there's any difference between expr_2021 and expr, so just use expr.

@github-actions github-actions bot added A-linter Area - Linter A-parser Area - Parser A-semantic Area - Semantic A-cfg Area - Control Flow Graph A-ast-tools Area - AST tools labels May 18, 2025
Copy link
Member Author


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.

@github-actions github-actions bot added the C-cleanup Category - technical debt or refactoring. Solution not expected to change behavior label May 18, 2025
@overlookmotel overlookmotel marked this pull request as ready for review May 18, 2025 10:18
@graphite-app graphite-app bot added the 0-merge Merge with Graphite Merge Queue label May 18, 2025
@graphite-app
Copy link
Contributor

graphite-app bot commented May 18, 2025

Merge activity

…1113)

Pure refactor. `expr_2021` fragment specifier was I assume introduced in these macros by a codemod when we updated to Rust 2024 edition. None of these macros are used with input where there's any difference between `expr_2021` and `expr`, so just use `expr`.
@graphite-app graphite-app bot force-pushed the 05-18-refactor_various_update_macros_to_use_expr_fragment_specifier branch from cce346b to bb8bde3 Compare May 18, 2025 10:26
@codspeed-hq
Copy link

codspeed-hq bot commented May 18, 2025

CodSpeed Instrumentation Performance Report

Merging #11113 will improve performances by 3.02%

Comparing 05-18-refactor_various_update_macros_to_use_expr_fragment_specifier (bb8bde3) with main (0a66cb0)

Summary

⚡ 1 improvements
✅ 37 untouched benchmarks

Benchmarks breakdown

Benchmark BASE HEAD Change
mangler[RadixUIAdoptionSection.jsx] 17.5 µs 17 µs +3.02%

@graphite-app graphite-app bot merged commit bb8bde3 into main May 18, 2025
23 checks passed
@graphite-app graphite-app bot removed the 0-merge Merge with Graphite Merge Queue label May 18, 2025
@graphite-app graphite-app bot deleted the 05-18-refactor_various_update_macros_to_use_expr_fragment_specifier branch May 18, 2025 10:33
@overlookmotel
Copy link
Member Author

mangler[RadixUIAdoptionSection.jsx] 17.5 µs 17 µs +3.02%

This benchmark result is spurious. Just noise.

This was referenced May 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-ast-tools Area - AST tools A-cfg Area - Control Flow Graph A-linter Area - Linter A-parser Area - Parser A-semantic Area - Semantic C-cleanup Category - technical debt or refactoring. Solution not expected to change behavior

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants