[#107430] [Ruby master Feature#18566] Merge `io-wait` gem into core IO — "byroot (Jean Boussier)" <noreply@...>
Issue #18566 has been reported by byroot (Jean Boussier).
22 messages
2022/02/02
[ruby-core:107525] [Ruby master Feature#18566] Merge `io-wait` gem into core IO
From:
"nobu (Nobuyoshi Nakada)" <noreply@...>
Date:
2022-02-09 09:38:46 UTC
List:
ruby-core #107525
Issue #18566 has been updated by nobu (Nobuyoshi Nakada). That warning will be just a noice, for users of a library using io-wait. It should be only when `Warning[:deprecate]` is true. ---------------------------------------- Feature #18566: Merge `io-wait` gem into core IO https://bugs.ruby-lang.org/issues/18566#change-96436 * 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:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>