Bug #13691: Word- and symbol array literals not valid where regular array is

• Status: Rejected
• Assignee: -
• Target version: -
• ruby -v: ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin16]
• Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN

[ted (Ted Johansson)]

Not sure if this is a limitation of the design space in the parser, or just a missed edge case. (Note that a regular array literal works fine.)

Steps to reproduce:

Run ruby -c on:

hoge %i(a b) { piyo }

Expected behaviour:

Syntax OK

Actual behaviour:

syntax error, unexpected '{', expecting end-of-input

[shevegen (Robert A. Heiler)]

Hmm you are right. That's interesting. I may be wrong but this may possibly be a limitation of the
parser, otherwise the ruby core team would have probably made it possible. (Though of course there
can be other reasons too... lack of resources... or nobody noticed this yet).

def foo(*i); pp i; end # => :foo
foo [:a, :b]  { piyo } # => [[:a, :b]]
foo  %i(a b)  { piyo } # => SyntaxError: (irb):14: syntax error, unexpected '{', expecting end-of-input foo  %i(a b) { piyo }
[:a, :b] ==  %i(a b)   # => true

Interesting find though, anyway!

[nobu (Nobuyoshi Nakada)]

• Is duplicate of Bug #505: 1.upto 2 {|i| p i } added

[nobu (Nobuyoshi Nakada)]

• Related to Bug #13547: [].delete 1 { 'NG' } added

[nobu (Nobuyoshi Nakada)]

Because of the precedence, {} is bound to %i() here, and %i() literal cannot be a method call.

[wanabe (_ wanabe)]

• Related to Bug #14023: SyntaxError on array argument and block added

[jeremyevans0 (Jeremy Evans)]

• Status changed from Open to Rejected