From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS63949 194.195.248.0/21 X-Spam-Status: No, score=-3.1 required=3.0 tests=AWL,BAYES_00,SPF_HELO_NONE, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from mail.oriontransfer.net (mail.oriontransfer.net [194.195.253.146]) by dcvr.yhbt.net (Postfix) with ESMTP id 767651F452 for ; Mon, 28 Aug 2023 23:12:53 +0000 (UTC) Received: from smtpclient.apple (unknown [203.86.197.151]) by mail.oriontransfer.net (Postfix) with ESMTPSA id CA9F32AFB9; Mon, 28 Aug 2023 23:12:51 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\)) Subject: Re: Ruby 3.3 compatible release? From: Samuel Williams In-Reply-To: <20230828010557.M452665@dcvr> Date: Tue, 29 Aug 2023 11:12:40 +1200 Cc: raindrops-public@yhbt.net Content-Transfer-Encoding: quoted-printable Message-Id: <2B638BF0-B5C2-4AFC-9C65-C950F81E914A@oriontransfer.co.nz> References: <20230828010557.M452665@dcvr> To: Eric Wong X-Mailer: Apple Mail (2.3731.700.6) List-Id: > 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=E2=80=99s also easier for other = implementations e.g. JRuby, TruffleRuby, which don=E2=80=99t 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=E2=80=99t 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=