fix(linter/no-unused-private-class-members): handle sequence expression correctly

[camc314]

Closes #17121

[camc314]

• fix(linter/no-unused-private-class-members): handle sequence expression correctly #17127 👈 (View in Graphite)
• main

---

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.

[camc314]

Merge activity

• Dec 19, 12:51 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Dec 19, 12:56 PM UTC: camc314 added this pull request to the Graphite merge queue.
• Dec 19, 1:01 PM UTC: Merged by the Graphite merge queue.

[Copilot]

Pull request overview

This PR fixes the handling of sequence expressions in the no-unused-private-class-members linter rule. Previously, private class members accessed within sequence expressions (e.g., (0, this.#field)) were incorrectly flagged as unused.

Key changes:

• Added AstKind::SequenceExpression(_) to the list of value contexts where private members are considered "read"
• Added a test case validating that private members used in sequence expressions are properly recognized as being used

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codspeed-hq]

CodSpeed Performance Report

Merging #17127 will not alter performance

_{Comparing c/12-19-fix_linter_handle_sequence_expression_in_no-unused-private-class-members (e42b6f9) with main (b87600a)}

Summary

✅ 4 untouched
⏩ 41 skipped¹

Footnotes

1. 41 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. ↩