@rubinius it seems like ConditionVariables should just map directly to pthread_cond_*. I'm going to try that with a MRI extension
-
-
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 I have a "fastcondition" gem where I wanted to spike out and measure pthread_cond-based ConditionVariables1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@seancribbs@rubinius Let me know if you need any help. I've worked with the GVL management functions a bunch.2 replies 0 retweets 0 likes
@evanphx @seancribbs @rubinius will do, thanks! Hopefully this problem can be solved in pure Ruby
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.