Project

General

Profile

Actions

Bug #12568

closed

wrong ArgumentError if an array is given for instance_exec with optional argument

Added by naruse (Yui NARUSE) over 7 years ago. Updated over 7 years ago.

Status:
Closed
Assignee:
-
Target version:
-
ruby -v:
ruby 2.4.0dev (2016-07-08 trunk 55607) [x86_64-darwin15]
[ruby-core:76300]

Description

From Ruby 2.2 to trunk, it wrongly raise ArgumentError as follows:

Sample code:

instance_exec([1,2,3]){|a| p a}
instance_exec([1,2,3]){|a=[]| p a}
instance_exec([1,2,3], &->(a){ p a })
->(a=[]){ p a }.to_proc.call([1,2,3])
instance_exec([1,2,3], &->(a=[]){ p a })

Expected result:

[1, 2, 3]
[1, 2, 3]
[1, 2, 3]
[1, 2, 3]
[1, 2, 3]

Actual result:

[1, 2, 3]
[1, 2, 3]
[1, 2, 3]
[1, 2, 3]
test.rb:7:in `block in <main>': wrong number of arguments (given 3, expected 0..1) (ArgumentError)
	from test.rb:7:in `instance_exec'
	from test.rb:7:in `<main>'

This issue affect https://github.com/rails/rails/pull/25699


Related issues 1 (0 open1 closed)

Is duplicate of Ruby master - Bug #10687: ArgumentError in certain cases of instance_exec (new bug in 2.2)ClosedActions
Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0