How does write barrier work in Ruby GC internals?

Write barriers track references between old and young objects to maintain GC correctness.

In generational GC, if an old object references a young object, GC must know it to avoid collecting it incorrectly. Write barriers intercept pointer updates and mark modified objects in a remembered set. This ensures minor GC can safely ignore old generation except for recorded references.