[ruby-core:118826] [Ruby master Bug#20671] Do not show "unused block" warning on `send`

Issue #20671 has been reported by ko1 (Koichi Sasada). ---------------------------------------- Bug #20671: Do not show "unused block" warning on `send` https://bugs.ruby-lang.org/issues/20671 * Author: ko1 (Koichi Sasada) * Status: Open * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Let's disable "unused block" warning on `send` because now it is hard to recognize the calling method accepts a block or not for general framework. Now test/unit has this problem. ```ruby require 'test/unit' class T < Test::Unit::TestCase def setup end def test_foo = nil end #=> /home/ko1/ruby/install/master/lib/ruby/gems/3.4.0+0/gems/test-unit-3.6.2/lib/test/unit/fixture.rb:284: warning: the block passed to 'priority_setup' defined at /home/ko1/ruby/install/master/lib/ruby/gems/3.4.0+0/gems/test-unit-3.6.2/lib/test/unit/priority.rb:183 may be ignored ``` Implementation: https://github.com/ruby/ruby/pull/11349 I think we can revisit it when we provide a way to recognize the calling method may accept a block or not. But now the relaxed behavior is better I think. -- https://bugs.ruby-lang.org/

Issue #20671 has been updated by ko1 (Koichi Sasada). Status changed from Open to Closed Matz accepted this idea so now I merged it. ---------------------------------------- Bug #20671: Do not show "unused block" warning on `send` https://bugs.ruby-lang.org/issues/20671#change-109399 * Author: ko1 (Koichi Sasada) * Status: Closed * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Let's disable "unused block" warning on `send` because now it is hard to recognize the calling method accepts a block or not for general framework. Now test/unit has this problem. ```ruby require 'test/unit' class T < Test::Unit::TestCase def setup end def test_foo = nil end #=> /home/ko1/ruby/install/master/lib/ruby/gems/3.4.0+0/gems/test-unit-3.6.2/lib/test/unit/fixture.rb:284: warning: the block passed to 'priority_setup' defined at /home/ko1/ruby/install/master/lib/ruby/gems/3.4.0+0/gems/test-unit-3.6.2/lib/test/unit/priority.rb:183 may be ignored ``` Implementation: https://github.com/ruby/ruby/pull/11349 I think we can revisit it when we provide a way to recognize the calling method may accept a block or not. But now the relaxed behavior is better I think. -- https://bugs.ruby-lang.org/
participants (1)
-
ko1 (Koichi Sasada)