From: "vipulnsward (Vipul Amler)" <vipulnsward@...>
Date: 2013-03-16T05:36:16+09:00
Subject: [ruby-core:53461] [CommonRuby - Feature #8096] introduce Time.current_timestamp


Issue #8096 has been updated by vipulnsward (Vipul Amler).


=begin
It could be any number of purposes. On top of my head I could think of remote systems, timestamps persisted to Databases, Event marking, Security Systems, Time conversions, etc (Although these are very bad examples)

Maybe http://en.wikipedia.org/wiki/Timestamping_(computing) or something similar would shed more light on this. 
=end
----------------------------------------
Feature #8096: introduce Time.current_timestamp
https://bugs.ruby-lang.org/issues/8096#change-37644

Author: vipulnsward (Vipul Amler)
Status: Feedback
Priority: Low
Assignee: 
Category: 
Target version: 


=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/