Introduce trait constraints; simplify elsewhere #445
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.
This PR introduces constraints to the
Time
andDiff
associated types forTraceReader
,BatchReader
, andCursor
. They look roughly like so:These constraints are .. pretty much the rule now, in use of differential dataflow. Users end up needing to write
where
clauses with much of this information, even though no one expects to use these things in the absence of these properties.