perf: optimize function_with_body_direct_function_with_body_callees #9292
+15 −13
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.
Summary
Optimizes
function_with_body_direct_function_with_body_calleesby replacingcollect::<Maybe<Vec<Option<_>>>>()?+flatten()with direct iteration. ProcessesMaybe<Option<_>>in a single pass, collecting onlySomevalues and avoiding an intermediate vector.Type of change
Please check one:
Why is this change needed?
The previous implementation created an intermediate
Vec<Option<_>>with all values (includingNone), then filtered in a second pass. This caused unnecessary allocations and two passes over the data.What was the behavior or documentation before?
Used
collect::<Maybe<Vec<Option<_>>>>()?+flatten(), creating an intermediate vector and iterating twice.What is the behavior or documentation after?
Uses direct iteration in a single pass, collecting only
Somevalues directly into the result set.Related issue or discussion (if any)
Additional context
The same pattern exists in
db.rs, but this PR addresses only the confirmed issue incycles.rs. All tests pass (62 passed).