kgio RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Samuel Williams <>
To: Eric Wong <>
Subject: Re: Ruby 3.3 compatible release?
Date: Tue, 29 Aug 2023 11:34:29 +1200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20230828005810.M622269@dcvr>

> On 28/08/2023, at 12:58 PM, Eric Wong <> wrote:
> Are there any other incompatibilities that may happen for Ruby 3.3
> that we might have to deal with before December?  I don't want to
> have to scramble another release together if we make one too soon.

As far as I know, and have tested, there are no other incompatibilities, and I think the Ruby team has a high standard for avoiding such situations. It’s partly my fault for pushing forward with changes, but we didn’t know what incompatibilities, if any, would occur due to the changes. Ruby 3.3, w.r.t `io.h`, should be fully backwards compatible, with deprecations.

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

#define HAVE_RB_IO_T

This restores compatibility with kgio and unicorn.

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

I’ll follow up with `git format-patch` soon.

Warm regards,

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25  2:01 Ruby 3.3 compatible release? Samuel Williams
2023-08-28  0:58 ` Eric Wong
2023-08-28 23:34   ` 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:

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

  git send-email \ \ \ \ \

* 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).