ruby.git/spec/ruby/core/unboundmethod/shared/dup.rb, branch v4.0.3 The Ruby Programming Language Update to ruby/spec@affef93 2025-01-30T19:43:46+00:00 Andrew Konchin andry.konchin@gmail.com 2025-01-30T15:39:10+00:00 d7a5ad2a21f7d2c45e3fea674ff077bb0e2cadae 






proc.c: get rid of `CLONESETUP`
2024-02-12T17:31:48+00:00

Jean Boussier
byroot@ruby-lang.org

2024-02-12T11:03:36+00:00

de1a586ecc2ee7f465f0c0a69291054136a3a819

[Bug #20253]

All the way down to Ruby 1.9, `Proc`, `Method`, `UnboundMethod`
and `Binding` always had their own specific clone and dup routine.

This caused various discrepancies with how other objects behave
on `dup` and `clone. [Bug #20250], [Bug #20253].

This commit get rid of `CLONESETUP` and use the the same codepath
as all other types, so ensure consistency.

NB: It's still not accepting the `freeze` keyword argument on `clone`.

Co-Authored-By: Étienne Barrié <etienne.barrie@gmail.com>





[Bug #20253]

All the way down to Ruby 1.9, `Proc`, `Method`, `UnboundMethod`
and `Binding` always had their own specific clone and dup routine.

This caused various discrepancies with how other objects behave
on `dup` and `clone. [Bug #20250], [Bug #20253].

This commit get rid of `CLONESETUP` and use the the same codepath
as all other types, so ensure consistency.

NB: It's still not accepting the `freeze` keyword argument on `clone`.

Co-Authored-By: Étienne Barrié <etienne.barrie@gmail.com>