From: Eric Wong <normalperson@...>
Date: 2022-02-07T18:16:57+00:00
Subject: [ruby-core:107503] Re: [Ruby master Misc#18557] DevMeeting-2022-02-17

"byroot (Jean Boussier)" <noreply@ruby-lang.org> wrote:
> Issue #18557 has been updated by byroot (Jean Boussier).
> 
> 
> [Feature #18566] Merge `io-wait` gem into core `IO` class. (byroot)
>   - It's very small and any non-trivial IO code will require it.
>   - 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.

Please just keep lib/io/wait.rb stub empty indefinitely.  No
need for deprecation warning, just a no-op is fine and don't
cause pain for existing users.  I don't want to hurt:

1) users who aren't coders
2) users who lack permissions to change code
3) codebases which need to support both old/ancient Rubies + new ones

I'm looking at system-wide implications from distro-installed Rubies;
not from a webapp+bundler perspective.

>   - @normalperson suggest to do the same with `io-nonblock`.

Actually, Benoit suggested io-nonblock.  I suggested going beyond that :)

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>