Skip to content

Conversation

@straight-shoota
Copy link
Member

#16490 introduced Time::Instant with Time.instant as a replacement for Time.monotonic.

@jzakiya
Copy link

jzakiya commented Dec 30, 2025

Was there any discussion to just make it Time.now as in Ruby, for compatibility, or was it deliberately to make it different?

After all, Time.instant and Time.now literally say the same things, with the later being shorter.

Just wondering.

@Blacksmoke16
Copy link
Member

Blacksmoke16 commented Dec 30, 2025

To be clear, this is a deprecation related to the monotonic clock. Renaming Time.instant to Time.now wouldn't make sense because they represent different kinds of clocks.

There was #9275 to bring back Time.now instead of Time.local, which you can read through for why it was opt-ed not to do that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants