⚡️ Speed up function function_has_return_statement by 90%
#238
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📄 90% (0.90x) speedup for
function_has_return_statementincodeflash/discovery/functions_to_optimize.py⏱️ Runtime :
2.54 milliseconds→1.33 millisecond(best of220runs)📝 Explanation and details
Here’s a faster rewrite. The original code uses
ast.walk, which traverses the entire subtree, yielding all nodes. Our target is to determine if anyast.Returnexists; we can short-circuit the search as soon as we find one, so a custom DFS traversal is much faster.This custom loop avoids constructing and yielding the full list of nodes, and stops immediately once a return is found, improving both speed and memory usage especially for large ASTs.
All existing comments preserved (none required updating).
✅ Correctness verification report:
🌀 Generated Regression Tests Details
To edit these changes
git checkout codeflash/optimize-function_has_return_statement-maxgutzdand push.