[#109095] [Ruby master Misc#18888] Migrate ruby-lang.org mail services to Google Domains and Google Workspace — "shugo (Shugo Maeda)" <noreply@...>
Issue #18888 has been reported by shugo (Shugo Maeda).
16 messages
2022/06/30
[ruby-core:109028] [Ruby master Feature#18655] Merge `IO#wait_readable` and `IO#wait_writable` into core
From:
"ioquatix (Samuel Williams)" <noreply@...>
Date:
2022-06-21 02:29:50 UTC
List:
ruby-core #109028
Issue #18655 has been updated by ioquatix (Samuel Williams). I've made a PR to move `wait`, `wait_readable`, `wait_writable`, `wait_priority` to `io.c` with some minor compatibility and documentation improvements. https://github.com/ruby/ruby/pull/6036 ---------------------------------------- Feature #18655: Merge `IO#wait_readable` and `IO#wait_writable` into core https://bugs.ruby-lang.org/issues/18655#change-98143 * 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>