Issue #22328 has been updated by matz (Yukihiro Matsumoto). You are right, it was left by mistake. Let's deprecate `IO#wait_priority` in 4.1 with a warning and remove it in a later release. `io.wait(IO::PRIORITY, timeout)` does the same thing. Matz. ---------------------------------------- Bug #22328: Should IO#wait_priority be deprecated and then removed? https://bugs.ruby-lang.org/issues/22328#change-119366 * Author: sampokuokkanen (Sampo Kuokkanen) * Status: Open * Backport: 3.3: UNKNOWN, 3.4: UNKNOWN, 4.0: UNKNOWN ---------------------------------------- In #18655, IO#wait_readable, IO#wait_writable, IO#wait_priority, and IO#wait were moved from io/wait into core. However, in #18655 note 11, Matz wrote:

After the discussion, we will drop wait_priority, but others are accepted. https://bugs.ruby-lang.org/issues/18655#note-11 https://github.com/ruby/dev-meeting-log/blob/d16be491afb7f3c0d956a6445dcb17d...

IO#wait_priority is still present in core today. It does not seem to be used that much: https://github.com/search?type=code&q=.wait_priority+language%3ARuby&l=Ruby So my question is, should it be deprecated and removed? -- https://bugs.ruby-lang.org/