Generalize int-proxy keys and values to Copy + Ord - #891
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Allow int-proxy backends to choose
Copy + Ordkeys and values, with separate value types for each input or output.Use explicit start/key/end positions so window traversal does not require a minimum key.
Adapt the Vec and Corgi backends.
The library, existing int-proxy tests, and Corgi tests pass using the adjacent Timely checkout through a command-line Cargo patch.
The existing u64 benchmarks have median changes within 0.7% across churn, multimoment, propagation, and string-valued workloads, with three trials per version.