From: akr@... Date: 2020-07-20T03:33:30+00:00 Subject: [ruby-core:99230] [Ruby master Feature#16470] Issue with nanoseconds in Time#inspect Issue #16470 has been updated by akr (Akira Tanaka). Status changed from Open to Feedback As others already pointed, the original description of this issue misunderstand the actual Ruby behavior. `Time.utc(2007, 11, 1, 15, 25, 0, 123456.789)` creates a Time object which has 0.123456789000000004307366907596588134765625 as a fractional second because the exact value of float 123456.789 is 123456.789000000004307366907596588134765625. I think the description "This is different from the stored nanosecond: ..." is based on misunderstanding of actual Ruby behavior. So, it is difficult to determine actual problem. We'd like to hear. ---------------------------------------- Feature #16470: Issue with nanoseconds in Time#inspect https://bugs.ruby-lang.org/issues/16470#change-86614 * Author: andrykonchin (Andrew Konchin) * Status: Feedback * Priority: Normal * Assignee: matz (Yukihiro Matsumoto) ---------------------------------------- Ruby 2.7 added nanosecond representation to the return value of `Time#inspect` method. Nanosecond is displayed as `Rational` as in the following example: ```ruby t = Time.utc(2007, 11, 1, 15, 25, 0, 123456.789) t.inspect # => "2007-11-01 15:25:00 8483885939586761/68719476736000000 UTC" ``` The nanosecond value `8483885939586761/68719476736000000` can be expanded to `0.12345678900000001`. This is different from the stored nanosecond: ```ruby t.nsec # => 123456789 t.strftime("%N") # => "123456789" ``` I assume it isn't expected, and will be fixed. -- https://bugs.ruby-lang.org/ Unsubscribe: