Skip to content

Conversation

frankmcsherry
Copy link
Member

The Hash trait on timestamps was not used other than 1. to derive a Hash implementation for Capability<T> and 2. in support for various timestamp-indexed demo operators (delay, aggregate, etc). The bound is removed from the trait, and added to the implementations.

Part of an effort to minimize the per-record reasoning. Timestamps are an instance, not the main instance, but .. this came up.

/// By implementing this trait, you promise that the type's [PartialOrder] implementation
/// is compatible with [Ord], such that if `a.less_equal(b)` then `a <= b`.
pub trait Timestamp: Clone+Eq+PartialOrder+Debug+Send+Any+ExchangeData+Hash+Ord {
pub trait Timestamp: Clone+Eq+PartialOrder+Ord+Debug+Any+ExchangeData {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moved Ord around, and removed Send because it is implied by ExchangeData.


/// A summary of how a timestamp advances along a timely dataflow path.
pub trait PathSummary<T> : Clone+'static+Eq+PartialOrder+Debug+Default {
pub trait PathSummary<T> : Clone+Eq+PartialOrder+Debug+Default {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The 'static bound seems unneeded and isn't present in Timestamp, so trying out the removal.

@frankmcsherry frankmcsherry merged commit a263ae1 into TimelyDataflow:master Sep 17, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants