Skip to content

perf(estree/tokens): do not branch on presence of override twice#19721

Merged
graphite-app[bot] merged 1 commit intomainfrom
om/02-22-perf_estree_tokens_do_not_branch_on_presence_of_override_twice
Feb 25, 2026
Merged

perf(estree/tokens): do not branch on presence of override twice#19721
graphite-app[bot] merged 1 commit intomainfrom
om/02-22-perf_estree_tokens_do_not_branch_on_presence_of_override_twice

Conversation

@overlookmotel
Copy link
Member

@overlookmotel overlookmotel commented Feb 25, 2026

Small perf optimization. Previously we branched on whether an override is registered for a token twice. Move the logic around so we branch on this condition only once.

@github-actions github-actions bot added the C-performance Category - Solution not expected to change functional behavior, only performance label Feb 25, 2026
This was referenced Feb 25, 2026
Copy link
Member Author

overlookmotel commented Feb 25, 2026


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.

This was referenced Feb 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-linter-plugins Area - Linter JS plugins A-parser Area - Parser 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.

2 participants