[ruby-core:107939] [Ruby master Feature#18566] Merge `io-wait` and `io-nonblock` gems into core IO

Issue #18566 has been updated by byroot (Jean Boussier).


> I think we should only add require_ruby_version = "< 3.2" to io-wait gem after merging io-wait into core IO class

I believe this would cause unnecessary disruption at release time. Some gems will have transitive dependencies on `io-wait` and it may take months for them to update. IMO making the gem empty is better.

> I'm still not sure why reason to make io/wait.rb to stub file in the future.

Because lots of code have `require "io/wait"`, so having this stub would prevent hard breakage.

----------------------------------------
Feature #18566: Merge `io-wait` and `io-nonblock` gems into core IO
https://bugs.ruby-lang.org/issues/18566#change-96889

* Author: byroot (Jean Boussier)
* Status: Open
* Priority: Normal
----------------------------------------
I think we should reconsider status of `io-wait`, and consider simply merging it into core's `IO`.

According to @nobu it's only a gem for "historical" reasons.

Any non trivial IO code will likely make use of it, and it's just 400 lines of code.

Recently with the extraction of `net-protocol`, it was added add a dependency and that caused Ruby 3.1 compatibility issues with some gems (e.g. with [`mail`](https://github.com/mikel/mail/pull/1439)).

### Proposal

  - Merge `io-wait` into `io.c` for Ruby 3.2
  - Remove `io-wait` as a dependency of all gems maintained by `ruby-core` (e.g. `net-protocol`).
  - Publish a new `io-wait` version that is simply an empty gem.
  - Add a `lib/io/wait.rb` stub, with eventually a deprecation warning.

cc @eregon @headius @mame @ioquatix



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>