Rubyists: stop using ObjectSpace._id2ref! It's not even safe to use on MRI/CRuby because it tries to reconstitute objects based on a pointer address in the GC heap (obj.object_id). JRuby does not support it out of the box.
-
Verifies my suspicions about the implications.
I suppose it is weird to expose a memory unsafe method in a memory safe language like that
-
-
Officially, _id2ref has always been an internal API, but people figured out how to use it. object_id has always been broken since it's not actually idempotent.
-
Docs don't seem to imply that it's internal.
- 5 more replies
New conversation -
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.