> cabo (Carsten Bormann) wrote: > ... Right. The only interface Ruby provides to NaN values is via pack/unpack. >> - `pack("g")` completely discards any actual NaN value and always packs the same bytes for a NaN > ... Indeed. Th...cabo (Carsten Bormann)
`pack("G")`/`unpack("G")` works great with NaN values. However, - `pack("g")` completely discards any actual NaN value and always packs the same bytes for a NaN ("bug as implemented" in `VALUE_to_float`) Also: - `unpack("g")...cabo (Carsten Bormann)
naruse (Yui NARUSE) wrote in #note-10: > Since I want Ruby 3.1 to keep as much as compatibility for Ruby 3.0 to ensure application/library developer adopt Ruby 3, I’m negative to go Ruby 3.1 with Psych 4.0.0. Unfortunately, users wil...cabo (Carsten Bormann)
Thank you. So I gather `URI.open(url, **options)` becomes `URI(url).open(**options)` (Re the deprecation of old Ruby versions: users of gems often want to use them with whatever is on their OS, and that currently means we re...cabo (Carsten Bormann)
So what is code that needs to be portable to older Rubies supposed to call now? `URI.open` only works since 2.5. We need to support 2.3 and 2.4 as well. `OpenURI.open_uri` ? cabo (Carsten Bormann)
A typical example of the consequences of this 7-year old bug is https://github.com/cabo/kramdown-rfc2629/issues/27 Please wake up and fix this. Now. cabo (Carsten Bormann)
Note that RFC 7301 has published: http://tools.ietf.org/html/rfc7301 HTTP/2 is nearing completion and requires ALPN, so if Ruby wants to play in this space, ALPN needs to be done with high priority now. cabo (Carsten Bormann)