Skip to content

Conversation

@camchenry
Copy link
Member

@camchenry camchenry commented Oct 15, 2025

Simple refactor to only do a single call expression check instead of two.

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

camchenry commented Oct 15, 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.

@camchenry camchenry marked this pull request as ready for review October 15, 2025 21:07
@camchenry camchenry requested a review from camc314 as a code owner October 15, 2025 21:07
Copilot AI review requested due to automatic review settings October 15, 2025 21:07
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR optimizes the no_array_method_this_argument linter rule by performing the call expression type check once at the entry point instead of redundantly checking in each helper function.

  • Moved the CallExpression pattern match from helper functions to the run method
  • Updated helper function signatures to accept &CallExpression directly instead of &AstNode
  • Added CallExpression to the import list

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@camc314 camc314 self-assigned this Oct 15, 2025
@camc314 camc314 added the 0-merge Merge with Graphite Merge Queue label Oct 15, 2025
Copy link
Contributor

camc314 commented Oct 15, 2025

Merge activity

@codspeed-hq
Copy link

codspeed-hq bot commented Oct 15, 2025

CodSpeed Performance Report

Merging #14641 will not alter performance

Comparing 10-15-perf_linter_only_check_for_call_expr_once_in_unicorn_no-array-method-this_ (58e17ae) with main (c8ea37d)1

Summary

✅ 4 untouched
⏩ 33 skipped2

Footnotes

  1. No successful run was found on main (58e17ae) during the generation of this report, so c8ea37d was used instead as the comparison base. There might be some changes unrelated to this pull request in this report.

  2. 33 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

…od-this` (#14641)

Simple refactor to only do a single call expression check instead of two.
@graphite-app graphite-app bot force-pushed the 10-15-perf_linter_only_check_for_call_expr_once_in_unicorn_no-array-method-this_ branch from 44bc4df to 58e17ae Compare October 15, 2025 21:12
@graphite-app graphite-app bot merged commit 58e17ae into main Oct 15, 2025
20 checks passed
@graphite-app graphite-app bot deleted the 10-15-perf_linter_only_check_for_call_expr_once_in_unicorn_no-array-method-this_ branch October 15, 2025 21:16
@graphite-app graphite-app bot removed the 0-merge Merge with Graphite Merge Queue label Oct 15, 2025
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