Re: Ruby 3.3 compatible release?

[Samuel Williams <samuel.williams@oriontransfer.co.nz>]

> 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,
Samuel