[Enhancement] Optimize the time cost of critical path for IntervalSetEvaluator #1491
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.
Related to issue #1069 Though we have
recur_depth_to alleviate the time cost,recur_depth_is incremented upon enteringEval(IntervalSet)and decremented upon exiting:Assuming there are N variables, and each variable’s range depends on k other variables:
recur_depth_)The new commit introduced a visiting_vars_ based solution to reduce the complexity into O(N^2).
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.