RoutingPolicy: don't build deep unions #6433
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.
In very long routing policies, especially when they have lots of
continue statements, we might compile them into fairly complicated
structures with Call statements. Sets.union is a shallow operation that
never coalesces, so it seems plausible that building a deep union will
cause stack overflows on containment checks.
To fix this, materialize the sets as we go. This should not in practice
be very expensive unless we are in a case that would cause a stack
overflow with the prior approach.