ruby.git/internal/imemo.h, branch v4.0.3 The Ruby Programming Language use `SET_SHAREABLE` 2025-10-23T04:08:26+00:00 Koichi Sasada ko1@atdot.net 2025-09-24T20:50:05+00:00 bc00c4468e0054ca896d2b83d3020180915f64cf to adopt strict shareable rule. * (basically) shareable objects only refer shareable objects * (exception) shareable objects can refere unshareable objects but should not leak reference to unshareable objects to Ruby world 
to adopt strict shareable rule.

* (basically) shareable objects only refer shareable objects
* (exception) shareable objects can refere unshareable objects
  but should not leak reference to unshareable objects to Ruby world
Don't export rb_imemo_new 2025-09-16T12:35:45+00:00 Peter Zhu peter@peterzhu.ca 2025-09-15T15:24:23+00:00 809dfb861ef0599c2572f10236aaf25c2093f6af Nothing needs rb_imemo_new exported anymore. 
Nothing needs rb_imemo_new exported anymore.
Remove next field and unused method from tmpbuf 2025-09-15T23:08:13+00:00 John Hawthorn john@hawthorn.email 2025-09-15T21:30:33+00:00 e4f09a8c94e6e6d21a6dfa43f71d52e4096234d6 These used to be used by the parser 
These used to be used by the parser
Move rb_imemo_tmpbuf_new to imemo.c 2025-09-15T15:43:05+00:00 Peter Zhu peter@peterzhu.ca 2025-09-15T14:47:14+00:00 1e3e04cd657c35fdd8d95096195d6b72b64e516c 






Combine rb_imemo_tmpbuf_auto_free_pointer and rb_imemo_tmpbuf_new
2025-09-15T13:25:20+00:00

Peter Zhu
peter@peterzhu.ca

2025-09-13T18:10:57+00:00

b0ce1fd549a3227ef4d9f65e4cdf0df93e4adeb0












Remove useless field in rb_imemo_tmpbuf_t
2025-09-12T18:13:59+00:00

Peter Zhu
peter@peterzhu.ca

2025-09-12T13:32:30+00:00

a9b35b3a0777e299b27d039b4b09fe8bdc9984c8












Replace ROBJECT_EMBED by ROBJECT_HEAP
2025-08-27T10:41:07+00:00

Jean Boussier
jean.boussier@gmail.com

2025-08-26T15:43:11+00:00

5257e1298c4dc4e854eaa0a9fe5e6dc5c1495c91

The embed layout is way more common than the heap one,
especially since WVA.

I think it makes for more readable code to inverse the
flag.





The embed layout is way more common than the heap one,
especially since WVA.

I think it makes for more readable code to inverse the
flag.







Ensure T_OBJECT and T_IMEMO/fields have identical layout
2025-08-26T11:44:59+00:00

Jean Boussier
jean.boussier@gmail.com

2025-08-26T07:19:07+00:00

14bdf4b57dcd3169a8717dc893fd1e1be897deeb












imemo_fields: store owner object in RBasic.klass
2025-08-13T17:53:18+00:00

Jean Boussier
jean.boussier@gmail.com

2025-08-08T09:41:02+00:00

10aa4134d408cab7b5754f3dcac2e75a52962b7c

It is much more convenient than storing the klass, especially
when dealing with `object_id` as it allows to update the id2ref
table without having to dereference the owner, which may be
garbage at that point.





It is much more convenient than storing the klass, especially
when dealing with `object_id` as it allows to update the id2ref
table without having to dereference the owner, which may be
garbage at that point.







Make `RClass.cc_table` a managed object
2025-08-01T08:42:04+00:00

Jean Boussier
jean.boussier@gmail.com

2025-07-30T10:44:39+00:00

f2a7e48deadb9101d49c9b613abf5a83c9e1dd49

For now this doesn't change anything, but now that the table
is managed by GC, it opens the door to use RCU when in multi-ractor
mode, hence allow unsynchornized reads.





For now this doesn't change anything, but now that the table
is managed by GC, it opens the door to use RCU when in multi-ractor
mode, hence allow unsynchornized reads.