raindrops RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Samuel Williams <samuel.williams@oriontransfer.co.nz>
To: Eric Wong <e@80x24.org>
Cc: raindrops-public@yhbt.net
Subject: Re: Ruby 3.3 compatible release?
Date: Tue, 29 Aug 2023 11:12:40 +1200	[thread overview]
Message-ID: <2B638BF0-B5C2-4AFC-9C65-C950F81E914A@oriontransfer.co.nz> (raw)
In-Reply-To: <20230828010557.M452665@dcvr>

> If you can guarantee the Ruby doesn't introduce further
> incompatibilities (the longer the guarantee, the better).

The plan is as follows:

- Ruby 3.3: deprecations on `struct rb_io`.
- Ruby 3.4+: remove public visibility of `struct rb_io`.

The reason for this change is to make it possible for us to change the internal details of `struct rb_io`. It’s also easier for other implementations e.g. JRuby, TruffleRuby, which don’t necessarily have the same layout and need to emulate it for native extensions.

We just merged a PR in Ruby head which amounts to:

#define HAVE_RB_IO_T

This restores the previous code path and makes Ruby 3.3 more compatible with existing code.

That being said, I think it would be great to merge the appropriate fixes which remove usage of deprecated fields in Ruby 3.3.

So to summarise, Ruby 3.3 should be compatible, but with deprecations. We don’t plan on introducing any further breaking changes until a later release (e.g 3.4 or later). If you can merge and release the appropriate patches, that would be greatly appreciated.

Warm regards,

      reply	other threads:[~2023-08-28 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25  1:51 Ruby 3.3 compatible release? Samuel Williams
2023-08-28  1:05 ` Eric Wong
2023-08-28 23:12   ` Samuel Williams [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://yhbt.net/raindrops/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2B638BF0-B5C2-4AFC-9C65-C950F81E914A@oriontransfer.co.nz \
    --to=samuel.williams@oriontransfer.co.nz \
    --cc=e@80x24.org \
    --cc=raindrops-public@yhbt.net \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).