[#62904] [ruby-trunk - Feature #9894] [Open] [RFC] README.EXT: document rb_gc_register_mark_object — normalperson@...
Issue #9894 has been reported by Eric Wong.
3 messages
2014/06/02
[#63321] [ANN] ElixirConf 2014 - Don't Miss Jos辿 Valim and Dave Thomas — Jim Freeze <jimfreeze@...>
Just a few more weeks until ElixirConf 2014!
6 messages
2014/06/24
[ruby-core:63083] Re: [CommonRuby - Feature #8259] Atomic attributes accessors
From:
Eric Wong <normalperson@...>
Date:
2014-06-10 21:50:03 UTC
List:
ruby-core #63083
thedarkone2@gmail.com wrote: > I am all for addition of `ConcurrentHash` or `Concurrent::Array` (these > new data structures would have `cas` and `swap` methods), but for > performance reasons plain old `Hash` and `Array` should be kept > completely un-thread-safe. Does that mean segfaulting the VM on concurrent Hash or Array access is OK? I don't think any current Ruby VM allows that. If we need to prevent segfaults on concurrent access, I suspect we'll need to pay some concurrency costs. Personally, I'm OK if we allow the VM to segfault on concurrent accesses, but I doubt others will agree with me.