Issue #8096 has been updated by naruse (Yui NARUSE).

Assignee set to matz (Yukihiro Matsumoto)

headius (Charles Nutter) wrote:
> This is now provided by #8658 in 2.1, but according to matz in the developer meeting notes linked there, Process::clock_gettime is not considered "spec".
> 
> So I'm not sure if this can be closed or not...we need to decide.
> 
> Optimistically assigning to akr.

Process.clock_gettime is low level API; it is different from this high level API.
On the meeting, matz considered this high level API didn't get consensus yet.
----------------------------------------
Feature #8096: introduce Time.current_timestamp
https://bugs.ruby-lang.org/issues/8096#change-42197

Author: vipulnsward (Vipul Amler)
Status: Feedback
Priority: Low
Assignee: matz (Yukihiro Matsumoto)
Category: 
Target version: Ruby 2.1.0


=begin
A lot of scenarios and applications require the use of (({Time.now.to_i})) which is used as current_timestamp in systems.

The introduction of (({Time.current_timestamp})) {or something with similar with different name} would provide implicit integer timestamp instead of going from 
(({Time.now})) -> time_object -> to_i -> integer timestamp value

So instead of

 Time.now.to_i # Outputs => 1363274618

one could use

 Time.current_timestamp # Outputs => 1363274618

=end



-- 
http://bugs.ruby-lang.org/