[ruby-core:88678] Re: [Ruby trunk Misc#15014] thread.c: use rb_hrtime_scalar for high-resolution time operations

From: Koichi Sasada <ko1@...>
Date: 2018-08-27 07:33:10 UTC
List: ruby-core #88678
On 2018/08/27 16:16, Eric Wong wrote:
> Yep.  Maybe some small systems can benefit with
> usec/msec resolution and uint32_t, though.

My comment is, if it assumes uint64_t, it is worth to write it 
explicitly (I verified this years with `2^64/ (1000 * 1000 * 1000 * 60 * 
60 * 24 * 365)` on google, but it will help for readers).

>>> MY_RUBY_BUILD_MAY_TIME_TRAVEL
>>
>> what is this?
> 
> A joke; at least as far as we know it is a joke :>

I'm not sure why uint64_t doesn't solve time machine problem and 
uint128_t solves it. Any RFC arguing it? (time machines should not leap 
1.0790283e+22 years)?

Beside joking, I misunderstand that some systems can change the machine 
time (time machine may means it) which affect monotonic time, and I 
could not understand why uint128 can solve such system issue.

-- 
// SASADA Koichi at atdot dot net

Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread