From: nagachika00@...
Date: 2015-08-14T07:50:01+00:00
Subject: [ruby-core:70385] [Ruby trunk - Bug #11283] Block assigned	implicitly

Issue #11283 has been updated by Tomoyuki Chikanaga.

Backport changed from 2.0.0: WONTFIX, 2.1: REQUIRED, 2.2: REQUIRED to 2.0.0: WONTFIX, 2.1: REQUIRED, 2.2: WONTFIX

The change of define_method's behavior is added into NEWS file at r50971. I think this is a spec change even thought original behavior is confusing.

----------------------------------------
Bug #11283: Block assigned implicitly
https://bugs.ruby-lang.org/issues/11283#change-53788

* Author: Andrew Kozin
* Status: Closed
* Priority: Normal
* Assignee: 
* ruby -v: 1.9.3, 2.0, 2.1, 2.2, ruby-head
* Backport: 2.0.0: WONTFIX, 2.1: REQUIRED, 2.2: WONTFIX
----------------------------------------
That is how it works:

    module Test
      def self.build(&block)
        klass = Class.new(Object)
        klass.__send__(:define_method, :foo)
        klass.__send__(:define_method, :bar)
        klass
      end
    end

    Tested = Test.build { :foo }
    # warning: tried to create Proc object without a block
    # => Tested
    Tested.new.foo
    # => :foo
    Tested.new.bar
    # => :foo

The block is assigned to all calls to `:define_method` via `Object#__send__` implicitly, while it wasn't asked to.

The behaviour is tested under MRI 1.9.3, 2.0, 2.1, 2.2, ruby-head. It doesn't occur under rbx-2 and jruby (1.7, 9.0.0.0).

For the context look at this thread https://github.com/mbj/mutant/issues/356



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