fix(ssa refactor): recursive branch analysis #1759
Merged
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.
Description
Problem*
Resolves GH-1664
The existing implementation of
analyze_function
used a queue + stack-based approach to to associating a branch start with an end. I couldn't convince myself that there was a way to make this approach safe, so I've written a recursion-based alternative that passes the failing case surfaced by GH-1664.Summary*
This alternative recursion based-approach associates a branch start to its end at the point that a recursion exits, such that the association is encapsulated. A disadvantage to this approach is that it does result in extra allocations, because
visited
hash sets andStepper
s are allocated for each level of recursion.Documentation
This PR requires documentation updates when merged.
Additional Context
PR Checklist*
cargo fmt
on default settings.