[ruby-dev:52059] [Ruby master Bug#10436] ruby -c and ripper inconsistency: m(&nil) {}

["jemmai (Jemma Issroff) via ruby-dev" <ruby-dev@ml.ruby-lang.org>]

Issue #10436 has been updated by jemmai (Jemma Issroff).


This bug still exists on Ripper. Should we try revive @jeremyevans0's patch?

It is potentially worth noting that Prism creates a `ParseError`: "Multiple block arguments; only one block is allowed"

----------------------------------------
Bug #10436: ruby -c and ripper inconsistency: m(&nil) {}
https://bugs.ruby-lang.org/issues/10436#change-105301

* Author: akr (Akira Tanaka)
* Status: Open
* Priority: Normal
* ruby -v: ruby 2.2.0dev (2014-10-27 trunk 48168) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
m(&nil) {} というまちがったコードは
ruby -c でちゃんとエラーになるのに、
Ripper.sexp ではならないようです。

```
% cat z.rb 
m(&nil) {}
% ruby -c z.rb 
z.rb:1: both block arg and actual block given
% ruby -rripper -e 'p Ripper.sexp(STDIN.read)' < z.rb
[:program, [[:method_add_block, [:method_add_arg, [:fcall, [:@ident, "m", [1, 0]]], [:arg_paren, [:args_add_block, [], [:var_ref, [:@kw, "nil", [1, 3]]]]]], [:brace_block, nil, [[:void_stmt]]]]]]
% ruby -v
ruby 2.2.0dev (2014-10-27 trunk 48168) [x86_64-linux]
```


---Files--------------------------------
ripper-block_dup_check-10436.patch (2.2 KB)


-- 
https://bugs.ruby-lang.org/