Skip to content

Conversation

@overlookmotel
Copy link
Member

@overlookmotel overlookmotel commented Jun 24, 2025

Instead of iterating over allow and recalculating the static property name on each turn of the loop, check if the property name is allowed once it's already calculated with MemberExpression::static_property_info.

This PR also ensures that the fix made in #11879 works. If not stacked on top of that PR, one of the tests added in #11878 fails.

@github-actions github-actions bot added A-linter Area - Linter C-performance Category - Solution not expected to change functional behavior, only performance labels Jun 24, 2025
Copy link
Member Author

overlookmotel commented Jun 24, 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.

@codspeed-hq
Copy link

codspeed-hq bot commented Jun 24, 2025

CodSpeed Instrumentation Performance Report

Merging #11880 will not alter performance

Comparing 06-24-perf_linter_no-console_get_static_property_name_only_once (66dbf9d) with 06-24-fix_ast_memberexpression_static_property_info_use_cooked_not_raw_for_templateelement_s (fe78dcf)

Summary

✅ 38 untouched benchmarks

@camc314 camc314 added the 0-merge Merge with Graphite Merge Queue label Jun 24, 2025
Copy link
Contributor

camc314 commented Jun 24, 2025

Merge activity

Instead of iterating over `allow` and recalculating the static property name on each turn of the loop, check if the property name is allowed once it's already calculated with `MemberExpression::static_property_info`.

This PR also ensures that the fix made in #11879 works. If not stacked on top of that PR, one of the tests added in #11878 fails.
@graphite-app graphite-app bot force-pushed the 06-24-fix_ast_memberexpression_static_property_info_use_cooked_not_raw_for_templateelement_s branch from 25ee137 to fe78dcf Compare June 24, 2025 13:35
@graphite-app graphite-app bot force-pushed the 06-24-perf_linter_no-console_get_static_property_name_only_once branch from 942808a to 66dbf9d Compare June 24, 2025 13:36
@graphite-app graphite-app bot removed the 0-merge Merge with Graphite Merge Queue label Jun 24, 2025
Base automatically changed from 06-24-fix_ast_memberexpression_static_property_info_use_cooked_not_raw_for_templateelement_s to main June 24, 2025 13:42
@graphite-app graphite-app bot merged commit 66dbf9d into main Jun 24, 2025
25 checks passed
@graphite-app graphite-app bot deleted the 06-24-perf_linter_no-console_get_static_property_name_only_once branch June 24, 2025 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-linter Area - Linter C-performance Category - Solution not expected to change functional behavior, only performance

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants