path: root/ext/dl/mkcall.rb
diff options
authorJean Boussier <>2022-12-06 12:56:51 +0100
committerJean Boussier <>2022-12-08 18:46:16 +0100
commit73771e4b192f3db62efb854affdfc95babba1d35 (patch)
tree6f15d7fea885b5e639c82b51d5c3fd50b9200735 /ext/dl/mkcall.rb
parentb19490f75dd790f2f886df2c05ed8fba947326a9 (diff)
ObjectSpace.dump_all: dump shapes as wellHEADmaster
I see several arguments in doing so. First they use a non trivial amount of memory, so for various memory profiling/mapping tools it is relevant to have visibility of the space occupied by shapes. Then, some pathological code can create a tons of shape, so it is valuable to have a way to have a way to observe shapes without having to compile Ruby with `SHAPE_DEBUG=1`. And additionally it's likely much faster to dump then this way than to use `RubyVM::Shape`. There are however a few open questions: - Shapes can't respect the `since:` argument. Not sure what to do when it is provided. Would probably make sense to not dump them. - Maybe it would make more sense to have a separate `ObjectSpace.dump_shapes`? - Maybe instead `dump_all` should take a `shapes: false` argument? Additionally, `ObjectSpace.dump_shapes` is added for the use case of debugging the evolution of the shape tree.
Notes: Merged:
Diffstat (limited to 'ext/dl/mkcall.rb')
0 files changed, 0 insertions, 0 deletions