From: eregontp@... Date: 2020-02-07T13:26:09+00:00 Subject: [ruby-core:97090] [Ruby master Bug#16608] ConditionVariable#wait should return false when timeout exceeded Issue #16608 has been updated by Eregon (Benoit Daloze). shugo (Shugo Maeda) wrote in #note-3: > ko1 suggested Mutex#release (new version of Mutex#sleep) for backward compatibility. `release` sounds like `unlock` as in `acquire/release` is similar to `lock/unlock`. So I think we need a different name there. I'm not sure about backward compatibility, but I would think it's fine to change the return value here as probably almost nothing uses it. ---------------------------------------- Bug #16608: ConditionVariable#wait should return false when timeout exceeded https://bugs.ruby-lang.org/issues/16608#change-84196 * Author: shugo (Shugo Maeda) * Status: Assigned * Priority: Normal * Assignee: nobu (Nobuyoshi Nakada) * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN ---------------------------------------- The following program prints `false` on Ruby 1.8, but `true` on Ruby 1.9 or later. ``` require "monitor" m = Monitor.new c = m.new_cond m.synchronize { p c.wait(0.1) } ``` However, it's not critical because most programs check the condition after wait. -- https://bugs.ruby-lang.org/ Unsubscribe: