fix(linter/array-callback-return): false postive with throw stmt in callback

[camc314]

fixes #13256

[camc314]

• fix(linter/array-callback-return): false postive with throw stmt in callback #13264 👈 (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.

[Copilot]

Pull Request Overview

Fixes a false positive in the array-callback-return linter rule where callbacks containing throw statements were incorrectly flagged as missing return statements. The fix recognizes that throw statements provide explicit control flow termination equivalent to return statements.

• Added handling for throw statements as explicit return status in the return checker
• Added comprehensive test coverage for throw statement scenarios
• Added integration test case demonstrating the fix for array callback functions

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
return_checker.rs	Adds throw statement handling and unit tests for the return status checker
mod.rs	Adds integration test case for array callback with throw statement

---

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

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #13264 will not alter performance

_{Comparing c/08-22-fix_linter_array-callback-return_false_postive_with_throw_expr_in_callback (fd14b39) with main (648e939)¹}

Summary

✅ 34 untouched benchmarks

Footnotes

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

[camc314]

Merge activity

• Aug 22, 12:27 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Aug 22, 12:27 PM UTC: camc314 added this pull request to the Graphite merge queue.
• Aug 22, 12:31 PM UTC: Merged by the Graphite merge queue.