ruby.git/test/ruby/test_proc.rb, branch v3_2_11

merge revision(s) 29c480dd6fca993590c82078ba797e2c4e876ac7: [Backport #20853]

2024-11-10T03:55:34+00:00

	[Bug #20853] Fix Proc#hash to not change after compaction

	The hash value of a Proc must remain constant after a compaction, otherwise
	it may not work as the key in a hash table.

merge revision(s) 3874381c4483ba7794ac2abf157e265546f9bfa7: [Backport #19759]

2023-07-23T03:01:21+00:00

	Fix autosplat conditions to handle ruby2_keywords case

	Autosplat should not occur if there are two arguments but second
	argument is an array containing a ruby2_keywords splat. Only
	autosplat if a single argument to be yielded to the block, and there
	is no splatted flagged keyword hash passed.

	Fixes [Bug #19759]
	---
	 test/ruby/test_proc.rb | 26 ++++++++++++++++++++++++++
	 vm_args.c              |  3 ++-
	 2 files changed, 28 insertions(+), 1 deletion(-)

Raise RuntimeError if Kernel#binding is called from a non-Ruby frame

2022-04-07T02:14:03+00:00

Check whether the current or previous frame is a Ruby frame in
call_trace_func and rb_tracearg_binding before attempting to
create a binding for the frame.

Fixes [Bug #18487]

Co-authored-by: Alan Wu

Revert "Raise RuntimeError if Kernel#binding is called from a non-Ruby frame"

2022-04-01T14:22:49+00:00

This reverts commit 343ea9967e4a6b279eed6bd8e81ad0bdc747f254.

This causes an assertion failure with -DRUBY_DEBUG=1 -DRGENGC_CHECK_MODE=2

Do not autosplat array in block call just because keywords accepted

2022-03-30T18:03:56+00:00

If the block only accepts a single positional argument plus keywords,
then do not autosplat.  Still autosplat if the block accepts more
than one positional argument in addition to keywords.

Autosplatting a single positional argument plus keywords made sense
in Ruby 2, since a final positional hash could be used as keywords,
but it does not make sense in Ruby 3.

Fixes [Bug #18633]

Raise RuntimeError if Kernel#binding is called from a non-Ruby frame

2022-03-24T19:31:07+00:00

Check whether the current or previous frame is a Ruby frame in
call_trace_func before attempting to create a binding for the frame.

Fixes [Bug #18487]

Co-authored-by: Alan Wu

Make Proc#parameters support lambda keyword for returning parameters as if lambda

2022-03-17T18:52:02+00:00

This makes it easier to use Proc#parameters to build wrappers.

Implements [Feature #15357]

T#dup (T < Proc) should return T's object

2022-01-13T08:43:14+00:00

T#dup (T < Proc) returns Proc object (not T) from Ruby 1.9.
[Bug #17545]

Add support for anonymous rest and keyword rest argument forwarding

2021-12-30T22:37:42+00:00

This allows for the following syntax:

```ruby
def foo(*)
  bar(*)
end
def baz(**)
  quux(**)
end
```

This is a natural addition after the introduction of anonymous
block forwarding.  Anonymous rest and keyword rest arguments were
already supported in method parameters, this just allows them to
be used as arguments to other methods.  The same advantages of
anonymous block forwarding apply to rest and keyword rest argument
forwarding.

This has some minor changes to #parameters output.  Now, instead
of `[:rest], [:keyrest]`, you get `[:rest, :*], [:keyrest, :**]`.
These were already used for `...` forwarding, so I think it makes
it more consistent to include them in other cases.  If we want to
use `[:rest], [:keyrest]` in both cases, that is also possible.

I don't think the previous behavior of `[:rest], [:keyrest]` in
the non-... case and `[:rest, :*], [:keyrest, :**]` in the ...
case makes sense, but if we did want that behavior, we'll have to
make more substantial changes, such as using a different ID in the
... forwarding case.

Implements [Feature #18351]

Preserve the encoding of message from outer local variables

2021-10-29T09:53:57+00:00