From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-4.2 required=3.0 tests=ALL_TRUSTED,BAYES_00,
	DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no
	autolearn=ham autolearn_force=no version=3.4.6
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id 7D4AE1F406;
	Mon, 28 Aug 2023 01:05:57 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=80x24.org;
	s=selector1; t=1693184757;
	bh=7ixANf0wA6ePENxYaqdnz/QS1/u3dUbgW7j1iXPxIVg=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
	b=av8fiZnIewaTkkuqMmpFA/1NSR735WQcOKwltR3YzODtpPXNdJY2V2JMyOH39+HqO
	 DODWvJGvXiE5OznJcHf9Fp84IVWhC0m6R4P8DlGak5k4LiEvvCQmkUom8r8UQKN+Zg
	 gZZKKAtlHeENH3J1i3VZ1ejqLrl7IEwqRNZ9iP8M=
Date: Mon, 28 Aug 2023 01:05:57 +0000
From: Eric Wong <e@80x24.org>
To: Samuel Williams <samuel.williams@oriontransfer.co.nz>
Cc: raindrops-public@yhbt.net
Subject: Re: Ruby 3.3 compatible release?
Message-ID: <20230828010557.M452665@dcvr>
References: <EB00C729-D403-4C45-BCDD-1B47B55BD707@oriontransfer.co.nz>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <EB00C729-D403-4C45-BCDD-1B47B55BD707@oriontransfer.co.nz>
List-Id: <raindrops-public.yhbt.net>

Samuel Williams <samuel.williams@oriontransfer.co.nz> wrote:
> Hi Eric,
> 
> Thanks for your continued effort to maintain and support this gem.

I don't hate this gem as much as the others, but it's still
uncomfortable for me to hear praise.

> We are trying to clean up the `io.h` interface in Ruby 3.3 and
> would like to know if there is anything we can do to help with
> a release of Raindrops which supports the updated interface
> and removes usage of deprecated symbols.

As I wrote in kgio-public[1] about other Ruby 3.3+ changes.

I also wonder if st.h hash table usage is on the chopping block
at some point; and I'm also somewhat tempted to replace it
anyways since I'll probably want to use some of this outside of
Ruby.

> I believe we’ve supplied a patch, but it is not formally
> released yet. Is there anything we can do to help?

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


[1] https://yhbt.net/kgio-public/20230828005810.M622269@dcvr/