Allow Method objects to be Ractor shareable #12978
Conversation
❌ Tests Failed✖️1 test failed ✔️28740 tests passed 25/162 test sessions failed❌ Test session #4111141 failed ❌ Test session #4111143 failed ❌ Test session #4111145 failed ❌ Test session #4111147 failed ❌ Test session #4111148 failed ❌ Test session #4111151 failed ❌ Test session #4111158 failed ❌ Test session #4111162 failed ❌ Test session #4111169 failed ❌ Test session #4111171 failed ❌ Test session #4111177 failed ❌ Test session #4111179 failed ❌ Test session #4111180 failed ❌ Test session #4111184 failed ❌ Test session #4111187 failed ❌ Test session #4111190 failed ❌ Test session #4111192 failed ❌ Test session #4111200 failed ❌ Test session #4111201 failed ❌ Test session #4111205 failed ❌ Test session #4111211 failed ❌ Test session #4111224 failed ❌ Test session #4111269 failed ❌ Test session #4111277 failed ❌ Test session #4111280 failed |
8178190 to
a53b3ff
Compare
This is built on top of #12977 (itself just a rebase of #7182). The last commit, bbad067, has the noteable change.
This makes Method objects shareable via
Ractor.make_shareable, with similar semantics to making iseq procs shareable. That is, it will only be made shareable if the receiver is already frozen/shareable, otherwise it will raiseRactor::IsolationError.I'll file a redmine ticket, since the behaviour deserves to be discussed.