ruby.git/ext/monitor/lib, branch v4.0.2 The Ruby Programming Language [DOC] Monitor 2024-12-25T04:16:14+00:00 Nobuyoshi Nakada nobu@ruby-lang.org 2024-12-25T04:16:14+00:00 2acbf45d368e03f8a38906676b2e3e63f299c67d 






[DOC] Monitor
2024-12-25T01:30:40+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2024-12-25T01:30:40+00:00

e46314edd11d6807b603498150e0785c87d5d3a5












[DOC] Surface existing MonitorMixin documentation
2022-12-26T08:40:11+00:00

Marco Costa
marco.costa@datadoghq.com

2022-12-23T22:00:47+00:00

5e54c57d83949818200bcec069455d713be681ff












Use https instead of http
2020-07-28T10:51:54+00:00

Kazuhiro NISHIYAMA
zn@mbf.nifty.com

2020-07-28T10:51:07+00:00

946cd6c5348d7dd12ecc41e79c3ca9803d2ca7f0












Fix MonitorMixin when the super's initialize has kwargs
2020-07-17T23:37:18+00:00

Masataka Pocke Kuwabara
kuwabara@pocke.me

2020-07-11T07:01:05+00:00

8d2333019abb1f8ad882dadf9096f81e9f427c6e












Fix a typo [ci skip]
2020-04-03T05:37:28+00:00

Kazuhiro NISHIYAMA
zn@mbf.nifty.com

2020-04-03T05:37:28+00:00

810d66f3e7da3a5267974e3a3b952ec3e378049b












new_cond before mon_initialize
2019-12-04T04:36:41+00:00

Koichi Sasada
ko1@atdot.net

2019-12-04T04:36:41+00:00

c6e3db0c66312af1e932c21006437419efa9ac75

MonitorMixin#new_cond can be called before mon_initialize, so we
need to initialize `@monitor` before it.

https://bugs.ruby-lang.org/issues/16255#note-4





MonitorMixin#new_cond can be called before mon_initialize, so we
need to initialize `@monitor` before it.

https://bugs.ruby-lang.org/issues/16255#note-4







Fix documentation of `MonitorMixin#new_cond` [ci skip] (#2707)
2019-11-28T04:24:01+00:00

y-yagi
yuuji.yaginuma@gmail.com

2019-11-28T04:24:01+00:00

18953416def52824c46a68370c4b34f5b720ee3f

Since https://github.com/ruby/ruby/pull/2576,
`new_cond` uses the Monitor object, not the receiver.




Since https://github.com/ruby/ruby/pull/2576,
`new_cond` uses the Monitor object, not the receiver.






Native MonitorMixin::ConditionVariable#wait
2019-10-20T06:45:30+00:00

Koichi Sasada
ko1@atdot.net

2019-10-20T06:45:30+00:00

a236eaa762137d7cb32b8311e0ef9a74bbb0f385

MonitorMixin::ConditionVariable#wait can be interrupted just after
Monitor#exit_for_cond. So implementation in C.





MonitorMixin::ConditionVariable#wait can be interrupted just after
Monitor#exit_for_cond. So implementation in C.







delegate synchronize method
2019-10-20T05:21:04+00:00

Koichi Sasada
ko1@atdot.net

2019-10-20T05:21:04+00:00

a0a3c701816c2fe4ab6e940c6cf5638756ceb6dc

Delegate MonitorMixin#synchronize body to Monitor#synchronize.
It makes guarantee interrupt safe (because Monitor#synchronize is
written in C). I thought Ruby implementation is also safe, but I
got stuck failure <http://ci.rvm.jp/results/trunk_test@P895/2327639>
so that I introduce this fix to guarantee interrupt safe.





Delegate MonitorMixin#synchronize body to Monitor#synchronize.
It makes guarantee interrupt safe (because Monitor#synchronize is
written in C). I thought Ruby implementation is also safe, but I
got stuck failure <http://ci.rvm.jp/results/trunk_test@P895/2327639>
so that I introduce this fix to guarantee interrupt safe.