ruby.git/ext/objspace/lib, branch ruby_3_0 The Ruby Programming Language Fix ObjectSpace.dump(obj, output: :stdout) 2020-10-02T15:00:01+00:00 Kazuhiro NISHIYAMA zn@mbf.nifty.com 2020-10-02T09:19:04+00:00 d0a7189f26dcb185c76771823dcfd20d8d4a7e3e RDoc says `ObjectSpace.dump(obj, output: :stdout) # => nil`, but it returns STDOUT since fbba6bd4e3dff7a61965208fecae908f10c4edbe. I think it is unintentional change. 
RDoc says `ObjectSpace.dump(obj, output: :stdout)   # => nil`,
but it returns STDOUT since fbba6bd4e3dff7a61965208fecae908f10c4edbe.

I think it is unintentional change.
Parse ObjectSpace.dump_all / dump arguments in Ruby to avoid allocation noise 2020-09-15T16:18:13+00:00 Jean Boussier jean.boussier@gmail.com 2020-09-10T11:17:53+00:00 fbba6bd4e3dff7a61965208fecae908f10c4edbe [Feature #17045] ObjectSpace.dump_all should allocate as little as possible in the GC heap Up until this commit ObjectSpace.dump_all allocates two Hash because of `rb_scan_args`. It also can allocate a `File` because of `rb_io_get_write_io`. These allocations are problematic because `dump_all` dumps the Ruby heap, so it should try modify as little as possible what it is observing. 
[Feature #17045] ObjectSpace.dump_all should allocate as little as possible in the GC heap

Up until this commit ObjectSpace.dump_all allocates two Hash because of `rb_scan_args`.

It also can allocate a `File` because of `rb_io_get_write_io`.

These allocations are problematic because `dump_all` dumps the Ruby
heap, so it should try modify as little as possible what it is
observing.