Optimize search for possible expansion locations #77572
Open
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
None
Purpose of change
When choosing a possible expansion location, the list of locations is searched through twice for two different criteria.
Describe the solution
Iterate once, until each criterion is met independently.
Also update a called recipe search to be able to bail out early if a result is found.
Describe alternatives you've considered
Testing
I've been playing with this for a while.
Additional context
This is the third in a series of PRs breaking apart #77397