Clarify strict inequality in getTimeZoneTransition()
#3098
Merged
Conversation
This file contains 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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3098 +/- ##
=======================================
Coverage 96.05% 96.05%
=======================================
Files 21 21
Lines 9951 9951
Branches 1802 1802
=======================================
Hits 9558 9558
Misses 346 346
Partials 47 47 ☔ View full report in Codecov by Sentry. |
ptomato
approved these changes
Mar 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
While strict inequality of
tandepochNanosecondscan be surmised from behavior (without it,someDateTime.getTimeZoneTransition("previous") == someDateTime.getTimeZoneTransition("previous").getTimeZoneTransition("previous")), I think this is a little clearer at a quick glance.