ruby.git/spec/ruby/core/unboundmethod/shared, branch v4.0.4 The Ruby Programming Language Update to ruby/spec@d8bacef 2025-05-09T21:22:15+00:00 Andrew Konchin andry.konchin@gmail.com 2025-05-07T10:08:11+00:00 269ad29de95e41cc8a4eede84b98a81a6ff4f7b6 






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>







UnboundMethod only refer defined_class
2022-12-02T23:53:12+00:00

Koichi Sasada
ko1@atdot.net

2022-12-02T20:55:33+00:00

59e389af2893c0fcf8b2cfa008c9a16825bf56ff

UnboundMethod records caller's class, like `D` or `E` on the
following case:

```ruby
class C
  def foo = :foo
end

class D < C
end

class E < C
end

d = D.instance_method(:foo)
e = E.instance_method(:foo)
```

But `d` and `e` only refers `C#foo` so that UnboundMethod doesn't
record `D` or `E`. This behavior changes the following methods:

* `UnboundMethod#inspect` (doesn't show caller's class)
* `UnboundMethod#==` (`d == e` for example)

fix https://bugs.ruby-lang.org/issues/18798





UnboundMethod records caller's class, like `D` or `E` on the
following case:

```ruby
class C
  def foo = :foo
end

class D < C
end

class E < C
end

d = D.instance_method(:foo)
e = E.instance_method(:foo)
```

But `d` and `e` only refers `C#foo` so that UnboundMethod doesn't
record `D` or `E`. This behavior changes the following methods:

* `UnboundMethod#inspect` (doesn't show caller's class)
* `UnboundMethod#==` (`d == e` for example)

fix https://bugs.ruby-lang.org/issues/18798







Update to ruby/spec@4f59d86
2020-10-24T13:53:53+00:00

Benoit Daloze
eregontp@gmail.com

2020-10-24T13:52:37+00:00

148961adcd0704d964fce920330a6301b9704c25












Update to ruby/spec@c1b568b
2018-03-04T15:09:32+00:00

eregon
eregon@b2dd03c8-39d4-4d8f-98ff-823fe69b080e

2018-03-04T15:09:32+00:00

401b64c4e840bc8887219e9e445a64b3d5943656

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@62656 b2dd03c8-39d4-4d8f-98ff-823fe69b080e





git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@62656 b2dd03c8-39d4-4d8f-98ff-823fe69b080e







Move spec/rubyspec to spec/ruby for consistency
2017-09-20T20:18:52+00:00

eregon
eregon@b2dd03c8-39d4-4d8f-98ff-823fe69b080e

2017-09-20T20:18:52+00:00

1d15d5f08032acf1b7bceacbb450d617ff6e0931

* Other ruby implementations use the spec/ruby directory.
  [Misc #13792] [ruby-core:82287]

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59979 b2dd03c8-39d4-4d8f-98ff-823fe69b080e





* Other ruby implementations use the spec/ruby directory.
  [Misc #13792] [ruby-core:82287]

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59979 b2dd03c8-39d4-4d8f-98ff-823fe69b080e