You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d7bc897
Browse filesBrowse the repository at this point in the historyBrowse files
ref(time): Rename MonotonicClock to MonotonicTicker (JAVA-571)
The type promises less than "clock" suggests: a tick carries no unit and
no epoch, and only differences between two ticks from the same instance
mean anything. "Ticker" keeps it from reading like a source of wall-clock
time.
Deadline.after now rejects a negative amount, since a deadline that
starts out in the past is a sign error at the call site and passed()
already expresses that case deliberately.
Also drops the "state that has not been populated yet" framing from the
Deadline.passed javadoc, covers isAfter on two equal deadlines, and
rewrites the tick-zero test comment to name the last-updated-timestamp
pattern it is about, rather than leaving "sentinel of 0" to be read as a
deadline of 0.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@
10
10
11
11
### Internal
12
12
13
-
- Add an internal `MonotonicClock` abstraction with `Deadline` and `Stopwatch` primitives ([#6028](https://github.com/getsentry/sentry-java/pull/6028))
13
+
- Add an internal `MonotonicTicker` abstraction with `Deadline` and `Stopwatch` primitives ([#6028](https://github.com/getsentry/sentry-java/pull/6028))
0 commit comments