[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ruby-core
Subject:    [ruby-core:108107] [Ruby master Feature#18655] Merge `IO#wait_readable` and `IO#wait_writable` into 
From:       "ioquatix (Samuel Williams)" <noreply () ruby-lang ! org>
Date:       2022-03-29 12:12:30
Message-ID: redmine.journal-97071.20220329121230.7941 () ruby-lang ! org
[Download RAW message or body]

Issue #18655 has been updated by ioquatix (Samuel Williams).


I'm fine with that.

----------------------------------------
Feature #18655: Merge `IO#wait_readable` and `IO#wait_writable` into core
https://bugs.ruby-lang.org/issues/18655#change-97071

* Author: byroot (Jean Boussier)
* Status: Open
* Priority: Normal
----------------------------------------
Extracted from [Feature #18566].

The decision was made to consider the methods from `io-wait` and `io-nonblock` one by \
one.

I think `wait_readable` and `wait_writeable` should be fairly non-controversial. \
They're quite essential to use `IO#read_nonblock` and `IO#write_nonblock` \
effectively.

Proposed patch: https://github.com/ruby/ruby/pull/5694

NB: if we only merge some methods, then `io/wait` must test which methods it needs to \
define or not. For now I use a `if RUBY_VERSION >= "3.2"` check in `extconf.rb`, but \
there might be a better approach.




-- 
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>


[prev in list] [next in list] [prev in thread] [next in thread]