Flotsync's generic Kompact test probe needs to track pending absence checks until either a matching event arrives or the scheduled timeout completes. The natural implementation is to index pending checks by the ScheduledTimer returned from schedule_once and complete the matching check directly from the timer callback. In Kompact 0.12, ScheduledTimer is Eq but not Hash, so downstream code either keeps a linear pending list or introduces a separate local ID captured by the timer closure.\n\nIt would be useful if ScheduledTimer explicitly promised enough identity semantics for use as a map key, for example by deriving/implementing Hash as well as Eq, or by exposing a stable opaque key. The handle should remain opaque; the request is only for map-friendly equality/hash semantics so timer-driven component code can avoid linear scans without relying on internal UUID details.
Flotsync's generic Kompact test probe needs to track pending absence checks until either a matching event arrives or the scheduled timeout completes. The natural implementation is to index pending checks by the ScheduledTimer returned from schedule_once and complete the matching check directly from the timer callback. In Kompact 0.12, ScheduledTimer is Eq but not Hash, so downstream code either keeps a linear pending list or introduces a separate local ID captured by the timer closure.\n\nIt would be useful if ScheduledTimer explicitly promised enough identity semantics for use as a map key, for example by deriving/implementing Hash as well as Eq, or by exposing a stable opaque key. The handle should remain opaque; the request is only for map-friendly equality/hash semantics so timer-driven component code can avoid linear scans without relying on internal UUID details.