core: stdcm: limit the loop where we look for possible delays #10126
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.
We would keep looking for different "openings" even very far in the future. This limits both conflict detection calls and the early steps of edge building.
The speedup is actually really good (roughly dividing the computation time by 2).
In the previous version, we would do something like that: we look for "openings" infinitely far in the future, and it's only when checking for conflicts and engineering allowances that we would discard them. In this case (and in fact in most case), there's only one "opening" available without clear conflicts.