From: eregontp@... Date: 2020-06-22T17:24:50+00:00 Subject: [ruby-core:98915] [Ruby master Feature#16470] Issue with nanoseconds in Time#inspect Issue #16470 has been updated by Eregon (Benoit Daloze). One consideration here is performance. For instance `Time.at(Float)` is quite slow, due to going through Rational, etc. Could you measure the other methods you changed to see how they perform compared to before? ---------------------------------------- Feature #16470: Issue with nanoseconds in Time#inspect https://bugs.ruby-lang.org/issues/16470#change-86295 * Author: andrykonchin (Andrew Konchin) * Status: Open * 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: