Re:Ruby core classes aren't thread safe
by aardvark179 on Monday February 25, 2013 @04:25PM
(#5281915)
A GIL does not mean classes should ignore concurrency concerns, it's still possible to get odd behaviour from things like hash table implementations in a GIL based interpreter when inserting objects as you may end up thread switching mid operation.
What saves you most of the time is that it isn't worth switching threads too often so normally you get lucky.
What saves you most of the time is that it isn't worth switching threads too often so normally you get lucky.