[#107867] Fwd: [ruby-cvs:91197] 8f59482f5d (master): add some tests for Unicode Version 14.0.0 — Martin J. Dürst <duerst@...>
To everybody taking care of continuous integration:
3 messages
2022/03/13
[#108090] [Ruby master Bug#18666] No rule to make target 'yaml/yaml.h', needed by 'api.o' — duerst <noreply@...>
Issue #18666 has been reported by duerst (Martin D端rst).
7 messages
2022/03/28
[#108117] [Ruby master Feature#18668] Merge `io-nonblock` gems into core — "Eregon (Benoit Daloze)" <noreply@...>
Issue #18668 has been reported by Eregon (Benoit Daloze).
22 messages
2022/03/30
[ruby-core:108039] [Ruby master Feature#18655] Merge `IO#wait_readable` and `IO#wait_writable` into core
From:
"byroot (Jean Boussier)" <noreply@...>
Date:
2022-03-23 13:45:49 UTC
List:
ruby-core #108039
Issue #18655 has been reported by byroot (Jean Boussier). ---------------------------------------- Feature #18655: Merge `IO#wait_readable` and `IO#wait_writable` into core https://bugs.ruby-lang.org/issues/18655 * 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:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>