From: Samuel Williams <firstname.lastname@example.org>
Subject: Re: [PATCH] Prefer to use rb_io_descriptor in my_fileno
Date: Fri, 9 Jun 2023 20:01:46 +0900 [thread overview]
Message-ID: <2BDDCABE-72A7-44DA-8E4B-624AFC0A382B@oriontransfer.co.nz> (raw)
Eric, it’s part of CRuby’s public headers since 3.1 was released.
Introduced in 4b8903421828cb9d4de139180563ae8d8f04e1ab
Hope that helps.
> On 9/06/2023, at 7:16 PM, Eric Wong <email@example.com> wrote:
> In the case of this patch; I would also like to know which Ruby
> implementation(s) and version(s) it appears in; and evidence
> backing up that it's a supported public API we can depend on
> going forward.
next parent reply other threads:[~2023-06-09 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5679D720-AD66-4471-9061-625159E71514@oriontransfer.co.nz>
2023-06-09 11:01 ` Samuel Williams [this message]
2023-06-10 7:30 [PATCH] Prefer to use rb_io_descriptor in my_fileno Jean Boussier
2023-06-11 21:39 ` Eric Wong
-- strict thread matches above, loose matches on Subject: below --
2023-06-09 8:58 Samuel Williams
2023-06-09 10:16 ` Eric Wong
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 \
* 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).