From: Webhostingonedollar102@...
Date: 2019-01-30T10:17:27+00:00
Subject: [ruby-core:91336] [Ruby trunk Feature#15574] Prohibit to pass a block on super() implicitly

Issue #15574 has been updated by bican304 (josef bican).


I extremely like your article. I had numerous helpful things from this article. I truly value your endeavors [99 rs domain godaddy](https://www.webhostingonedollar.com/godaddy-rs-99-web-hosting-domain.html) for compose this post. A debt of gratitude is in order for offering that enlightening post to us.

----------------------------------------
Feature #15574: Prohibit to pass a block on super() implicitly
https://bugs.ruby-lang.org/issues/15574#change-76585

* Author: ko1 (Koichi Sasada)
* Status: Open
* Priority: Normal
* Assignee: matz (Yukihiro Matsumoto)
* Target version: 
----------------------------------------
As described in [Feature #15554], `super()` (not `super`) pass the given block.

```
class C
  def foo
    p block_given?
  end
end

class C1 < C
  def foo
    super   #=> true
    super() #=> true
  end
end

C1.new.foo{}
```

`super` (without parameters) passes all passed parameters so it is no surprise to pass given block. 

However, `super()` (with parameters. In this case, it passes 0 parameters) also pass given block implicitly.

I'm not sure who use this behavior, but I think it is simple to prohibit such implicit block passing.




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

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>