Issue #16608 has been updated by jeremyevans0 (Jeremy Evans).


I agree with @Eregon that we can probably change the return value of ConditionVariable#wait in Ruby 3.  As it always returns true currently, it's worthless and nothing should be relying on it.

I can see that changing `Mutex#sleep` to start returning `nil` could break things, though.  I think we do need a new method.  Maybe `Mutex#sleep_for` or `Mutex#sleep!`.

----------------------------------------
Bug #16608: ConditionVariable#wait should return false when timeout exceeded
https://bugs.ruby-lang.org/issues/16608#change-85845

* 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: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>