[#99115] [Ruby master Bug#17023] How to prevent String memory to be relocated in ruby-ffi — larskanis@...
Issue #17023 has been reported by larskanis (Lars Kanis).
22 messages
2020/07/10
[#99375] [Ruby master Feature#17055] Allow suppressing uninitialized instance variable and method redefined verbose mode warnings — merch-redmine@...
Issue #17055 has been reported by jeremyevans0 (Jeremy Evans).
29 messages
2020/07/28
[#101207] [Ruby master Feature#17055] Allow suppressing uninitialized instance variable and method redefined verbose mode warnings
— merch-redmine@...
2020/12/02
Issue #17055 has been updated by jeremyevans0 (Jeremy Evans).
[#101231] Re: [Ruby master Feature#17055] Allow suppressing uninitialized instance variable and method redefined verbose mode warnings
— Austin Ziegler <halostatue@...>
2020/12/03
What does this mean?
[ruby-core:99229] [Ruby master Feature#16470] Issue with nanoseconds in Time#inspect
From:
akr@...
Date:
2020-07-20 03:15:40 UTC
List:
ruby-core #99229
Issue #16470 has been updated by akr (Akira Tanaka).
There are several examples time needs more than nanoseconds.
* SQLite supports arbitrary number of digits in fractional seconds
https://www.sqlite.org/lang_datefunc.html
* POSIX pax format supports arbitrary number of digits in fractional seconds
http://pubs.opengroup.org/onlinepubs/007904875/utilities/pax.html#tag_04_100_13_05
* EXIF supports arbitrary number of digits in fractional seconds
http://www.exif.org/Exif2-1.PDF
* NTPv4's 128-bit date format has 64-bit fraction field : 2**(-64) second
https://tools.ietf.org/html/rfc5905#section-6
* FreeBSD has struct bintime which can represent 2**(-64) second
https://svnweb.freebsd.org/base/head/sys/sys/time.h?view=markup&pathrev=363193#l55
It is visible from userland for datagram timestamp
https://www.freebsd.org/cgi/man.cgi?query=setsockopt
Ruby supports it as converting bintime to Time object
* DB2 supports fractional seconds up to 12 digits in timestamp (12 digits represents picosecond)
https://www.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.sql.ref.doc/doc/r0008474.html
----------------------------------------
Feature #16470: Issue with nanoseconds in Time#inspect
https://bugs.ruby-lang.org/issues/16470#change-86613
* 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: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>