ruby.git/spec/ruby/core/proc/shared, branch v3_4_9 The Ruby Programming Language 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>
Update to ruby/spec@3fc4444 2024-02-05T15:29:57+00:00 Benoit Daloze eregontp@gmail.com 2024-02-05T15:29:57+00:00 40642cd3bc581d3bb402ea5e8e61cdfb868b4f68 






Update to ruby/spec@30e1c35
2023-06-26T13:55:11+00:00

Benoit Daloze
eregontp@gmail.com

2023-06-26T13:55:11+00:00

515bd4214497b3af02f6eef51b496ad9a0cf6b3b












Update to ruby/spec@c3677cf
2023-05-29T13:27:57+00:00

Benoit Daloze
eregontp@gmail.com

2023-05-29T13:27:57+00:00

c48d496e8cfdf8243d2beb28623954003adaf7fc












Update to ruby/spec@3affe1e
2022-04-25T12:53:54+00:00

Benoit Daloze
eregontp@gmail.com

2022-04-25T12:53:54+00:00

45cf4f218728a15eb36d14a6c9912086525f5e3f












Update to ruby/spec@b65d01f
2021-07-29T20:11:21+00:00

Benoit Daloze
eregontp@gmail.com

2021-07-29T20:11:21+00:00

6998d758248d778fa95b008c78d05473e48b8428












Update to ruby/spec@37e52e5
2021-02-27T12:00:26+00:00

Benoit Daloze
eregontp@gmail.com

2021-02-27T12:00:26+00:00

36dde35e029c7a6607e6c674062ce6fc7a51c0bd












Update to ruby/spec@ac878ad
2020-11-27T13:55:31+00:00

Benoit Daloze
eregontp@gmail.com

2020-11-27T13:55:31+00:00

f02d2f82bf10351f480ea312f40cb840e2437f93












Update to ruby/spec@b6b7752
2020-06-27T13:51:37+00:00

Benoit Daloze
eregontp@gmail.com

2020-06-27T13:51:37+00:00

b3fa158d1c4d8e03b8dc04f1e4f9940a8a4ef44c












Implement Proc#== and #eql?
2020-06-19T19:58:25+00:00

Jeremy Evans
code@jeremyevans.net

2020-06-01T19:28:05+00:00

878af5147def7fed089d3cc388742f0111db58ae

Previously, these were not implemented, and Object#== and #eql?
were used.  This tries to check the proc internals to make sure
that procs created from separate blocks are treated as not equal,
but procs created from the same block are treated as equal, even
when the lazy proc allocation optimization is used.

Implements [Feature #14267]





Previously, these were not implemented, and Object#== and #eql?
were used.  This tries to check the proc internals to make sure
that procs created from separate blocks are treated as not equal,
but procs created from the same block are treated as equal, even
when the lazy proc allocation optimization is used.

Implements [Feature #14267]