Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(parser): correct AST for #field in x << y #9039

Merged
merged 1 commit into from
Feb 11, 2025

Conversation

Boshen
Copy link
Member

@Boshen Boshen commented Feb 11, 2025

fixes #9034

@github-actions github-actions bot added A-parser Area - Parser C-bug Category - Bug labels Feb 11, 2025
Copy link
Member Author

Boshen commented Feb 11, 2025


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.

Copy link

codspeed-hq bot commented Feb 11, 2025

CodSpeed Performance Report

Merging #9039 will not alter performance

Comparing 02-11-fix_parser_correct_ast_for_field_in_x_y_ (662ab90) with main (567bc2c)

Summary

✅ 33 untouched benchmarks

@Boshen Boshen force-pushed the 02-11-fix_parser_correct_ast_for_field_in_x_y_ branch from 2af4f1b to ef2d7a3 Compare February 11, 2025 07:52
@github-actions github-actions bot added A-transformer Area - Transformer / Transpiler A-prettier Area - Prettier labels Feb 11, 2025
Copy link

graphite-app bot commented Feb 11, 2025

Merge activity

  • Feb 11, 2:58 AM EST: A user added this pull request to the Graphite merge queue.
  • Feb 11, 2:59 AM EST: The Graphite merge queue couldn't merge this PR because it had conflicts with the trunk branch.
  • Feb 11, 5:32 AM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
  • Feb 11, 5:32 AM EST: A user added this pull request to the Graphite merge queue.
  • Feb 11, 5:37 AM EST: A user merged this pull request with the Graphite merge queue.

@Boshen Boshen force-pushed the 02-11-fix_parser_correct_ast_for_field_in_x_y_ branch from ef2d7a3 to a57ffe8 Compare February 11, 2025 09:33
@overlookmotel overlookmotel added the 0-merge Merge with Graphite Merge Queue label Feb 11, 2025
@graphite-app graphite-app bot force-pushed the 02-11-fix_parser_correct_ast_for_field_in_x_y_ branch from a57ffe8 to 662ab90 Compare February 11, 2025 10:32
@graphite-app graphite-app bot merged commit 662ab90 into main Feb 11, 2025
27 checks passed
@graphite-app graphite-app bot deleted the 02-11-fix_parser_correct_ast_for_field_in_x_y_ branch February 11, 2025 10:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0-merge Merge with Graphite Merge Queue A-parser Area - Parser A-prettier Area - Prettier A-transformer Area - Transformer / Transpiler C-bug Category - Bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

parser: incorrect operator precedence of #field in x << y
2 participants