Re:Crystal: Fast as C, Slick as Ruby
by mike_hearn on Friday August 05, 2016 @09:00AM
(#12231921)
Bear in mind that's a conceptual description. The read/write barriers are implemented as compiler node graphs and thus can be optimised.
I'm a bit surprised that indirection is efficient enough to be worth the trouble (since you need reads and writes to branch for the indirected-object case), but I can't argue with results.