Planning processes #110
Open
Planning processes #110
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hunse
force-pushed
the
planning-processes
branch
3 times, most recently
from
bc1249c
to
a1e5042
Compare
These cannot be planned together, so the resulting operator plans are more efficient if we separate in the planner.
hunse
force-pushed
the
planning-processes
branch
from
a1e5042
to
c562665
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously, all Processes were treated the same, even though different types of processes can't be planned together. This PR splits that up so that different process types are treated differently.
TODO: some process types can be planned together, e.g. subclasses of LinearFilter. Allow them to be done together.