Support Ruby 3.3

[k0kubun]

Fix #77

This follows the example fix shown in [Feature #19057] at 94dbdd9497. I also changed #if HAVE_RB_IO_T to #if defined(HAVE_RB_IO_T) so that it will not print warnings when not defined.

[ioquatix]

Thanks for this!

@tarcieri if you don't want to maintain this gem, do you want to:

1. Transfer it to the socketry org
2. Add me as an owner on Rubygems

I can triage this issue and release.

LMK what you prefer to do.

[tarcieri]

Sure, that sounds good to me. Let's transfer it to socketry

[ioquatix]

Okay, I'll await your transfer.

[tarcieri]

It's transferred

[ioquatix]

Thanks @tarcieri do you mind adding me as an owner on Rubygems.org too? Thanks!

[tarcieri]

Invite sent

[ioquatix]

@k0kubun I want to add CI before we merge this PR, please give me a couple of days to sort it out.

[k0kubun]

Sure, that makes sense. Thank you for working on that.

[ioquatix]

@k0kubun I could not get this to pass CI, but master branch is passing. Do you mind taking a look if you have time?

[ioquatix]

(it might just be flaky test suite... I tried several times, even master is a bit unreliable).

[ioquatix]

This looks okay to me now. I think we should try to move fptr usage to old code path. Since ultimately we want to avoid it. Do you have time to make that change?

[k0kubun]

Well, two out of the three fptr references are used for rb_io_set_nonblock, which does expect fptr. I don't think it's the scope of this PR to move away from rb_io_set_nonblock.

[k0kubun]

Fixed the other one though 390ff4e. Only this one makes sense to me.

[ioquatix]

Thanks for your effort. I'll try to cut a release soon.

[ioquatix]

@k0kubun it sounds like you may have software using cool.io - can you test it with the latest release if so?

[k0kubun]

I upgraded cool.io to the released version on yjit-bench Shopify/yjit-bench@2858bc3.

The extension compiles correctly on Ruby master. The fluentd benchmark finishes successfully. I'm not sure if the benchmark goes through cool.io code, but at least bundle install is not broken anymore.