Ractor: don't invoke initialize_* callbacks when moving an object
#13023
Conversation
[Bug #20255] Alternatively we could invoke it, but would need to do it in the context of the newly spawned Ractor so that accessing global non-shareable objects is not possible.
❌ Tests Failed✖️27 tests failed ✔️28431 tests passed(4 flakes) 25/85 test sessions failed❌ Test session #4077791 failed ❌ Test session #4077793 failed ❌ Test session #4077796 failed ❌ Test session #4077797 failed  ❌ Test session #4077798 failed ❌ Test session #4077799 failed ❌ Test session #4077800 failed ❌ Test session #4077801 failed ❌ Test session #4077804 failed ❌ Test session #4077805 failed ❌ Test session #4077806 failed ❌ Test session #4077819 failed ❌ Test session #4077820 failed ❌ Test session #4077824 failed ❌ Test session #4077828 failed ❌ Test session #4077836 failed ❌ Test session #4077837 failed ❌ Test session #4077845 failed ❌ Test session #4077853 failed ❌ Test session #4077860 failed ❌ Test session #4077864 failed ❌ Test session #4077868 failed ❌ Test session #4077878 failed ❌ Test session #4077914 failed ❌ Test session #4077921 failed |
|
This isn't possible because class Array
def initialize_clone(o)
# noop
end
end
p [1, 2, 3, 4, 5].clone # => [] |
[Bug #20255]
Followup: #13008
Alternatively we could invoke it, but would need to do it in the context of the newly spawned Ractor so that accessing global non-shareable objects is not possible.
@ko1 @jhawthorn @tenderlove any opinion?