Skip to content

Implement the same ranges for all platforms #453

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 15 commits into from
Mar 3, 2025
Merged

Conversation

dkhalanskyjb
Copy link
Collaborator

@dkhalanskyjb dkhalanskyjb commented Oct 31, 2024

Fixes #432

@dkhalanskyjb dkhalanskyjb force-pushed the uniform-ranges branch 4 times, most recently from b7c293c to ae4373e Compare November 5, 2024 12:52
@dkhalanskyjb dkhalanskyjb marked this pull request as ready for review November 5, 2024 12:52
@dkhalanskyjb dkhalanskyjb requested a review from ilya-g November 5, 2024 12:52
Comment on lines 126 to 127
epochSeconds < MIN_SECOND -> MIN
epochSeconds > MAX_SECOND -> MAX
Copy link
Member

@ilya-g ilya-g Feb 20, 2025

Choose a reason for hiding this comment

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

Is it still possible? If the Instant range doesn't potentially fit in the Long range of milliseconds, doesn't it mean that the Long range of milliseconds always fits in the Instant range?

@dkhalanskyjb dkhalanskyjb merged commit 2e197e5 into master Mar 3, 2025
1 check passed
@dkhalanskyjb dkhalanskyjb deleted the uniform-ranges branch March 3, 2025 15:05
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.

Make admissible ranges the same on all platforms
4 participants