Hey @jruby and @rubinius, do you provide optimized ConditionVariables? Looking to reimplement MRI's for @celluloidrb due to perf regressions
-
-
Replying to @bascule2 replies 0 retweets 0 likes
-
Replying to @evanphx1 reply 0 retweets 0 likes
-
Replying to @bascule3 replies 0 retweets 0 likes
-
Replying to @seancribbs
@seancribbs@evanphx@rubinius Thread.handle_interrupt is terrible and makes me want to ditch ConditionVariable1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@seancribbs@rubinius How's it breaking CondVar?2 replies 0 retweets 0 likes -
Replying to @evanphx
@evanphx@seancribbs@rubinius we will keep using ConditionVariable on !MRI1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@seancribbs@rubinius Implementing your own binding to pthread_{mutex,condvar} is totally possible in a Cext.2 replies 0 retweets 0 likes
Replying to @evanphx
@evanphx @seancribbs @rubinius yep, that was the plan. But first just removing Thread.handle_interrupt from the pure Ruby ConditionVariable
6:34 PM - 28 Jun 2013
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.