[#109207] [Ruby master Feature#18915] New error class: NotImplementedYetError or scope change for NotImplementedYet — Quintasan <noreply@...>
Issue #18915 has been reported by Quintasan (Michał Zając).
18 messages
2022/07/14
[ruby-core:109273] [Ruby master Feature#18655] Copy `IO#wait_readable`, `IO#wait_writable`, `IO#wait_priority` and `IO#wait` into core.
From:
"matz (Yukihiro Matsumoto)" <noreply@...>
Date:
2022-07-21 05:23:22 UTC
List:
ruby-core #109273
Issue #18655 has been updated by matz (Yukihiro Matsumoto). After the discussion, we will drop `wait_priority`, but others are accepted. Matz. ---------------------------------------- Feature #18655: Copy `IO#wait_readable`, `IO#wait_writable`, `IO#wait_priority` and `IO#wait` into core. https://bugs.ruby-lang.org/issues/18655#change-98405 * Author: byroot (Jean Boussier) * Status: Closed * 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>