Discussion thread: here
Right now Streams API universally represents time as ms-since-unix-epoch.
There's nothing wrong, per se, with this, but Duration is more ergonomic for an API.
What we don't want is to present a heterogeneous API, so we need to make sure the whole Streams API is in terms of Duration.
Improve of semantics of
We need to add following method to public API.
- In this scope keep existing methods as is.
Try to reduce the visibility of methods in next tickets.
- Introduce finer methods with
- reject negative numbers
- make 0 just signal and return immediately (after checking the state once)
Compatibility, Deprecation, and Migration Plan