Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(experimental) RUBY_TYPED_FROZEN_SHAREABLE_NO_REC
T_DATAhas a flagRUBY_TYPED_FROZEN_SHAREABLEwhich meansif the
T_DATAobject is frozen, it can be sharable.On the
Ractor.make_sharable(obj), rechable objects from theT_DATAobject will be applyRactor.make_shareablerecursively.RUBY_TYPED_FROZEN_SHAREABLE_NO_RECis similar to theRUBY_TYPED_FROZEN_SHAREABLE, but doesn't applyRactor.make_sharablerecursively for children.
If it refers to unshareable objects, it will simply raise an error.
I'm not sure this pattern is common or not, so it is not in public.
If we find more cases, we can discuss publication.
Method and UnboundMethod can be sharable
with
RUBY_TYPED_FROZEN_SHAREABLE_NO_REC,if the receiver object is shareable on Method objects.