diff options
| author | Koichi Sasada <ko1@atdot.net> | 2025-12-05 01:13:55 +0900 |
|---|---|---|
| committer | Koichi Sasada <ko1@atdot.net> | 2025-12-05 02:28:30 +0900 |
| commit | f2cd772329b8d07e29ed114480ff99ad36acbd75 (patch) | |
| tree | 00ac3ee0d0f422ed458cc8a5abe6929086928e54 /include/ruby/thread.h | |
| parent | 3730022787086852fa2fbc94ffda6ec8c8fbc0b3 (diff) | |
(experimental) RUBY_TYPED_FROZEN_SHAREABLE_NO_REC
`T_DATA` has a flag `RUBY_TYPED_FROZEN_SHAREABLE` which means
if the `T_DATA` object is frozen, it can be sharable.
On the `Ractor.make_sharable(obj)`, rechable objects from the
`T_DATA` object will be apply `Ractor.make_shareable` recursively.
`RUBY_TYPED_FROZEN_SHAREABLE_NO_REC` is similar to the
`RUBY_TYPED_FROZEN_SHAREABLE`, but doesn't apply `Ractor.make_sharable`
recursively 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.
Diffstat (limited to 'include/ruby/thread.h')
0 files changed, 0 insertions, 0 deletions
