From: "decuplet (Nikita Shilnikov) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "decuplet (Nikita Shilnikov)" <noreply@ruby-lang.org>
Subject: [ruby-core:120476] [Ruby master Bug#21003] unexpected warning about ignored block
Date: Sat, 04 Jan 2025 13:41:17 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-21003.20250104134116.8259@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-21003.20250104134116.8259@ruby-lang.org>
Issue #21003 has been reported by decuplet (Nikita Shilnikov).
----------------------------------------
Bug #21003: unexpected warning about ignored block
https://bugs.ruby-lang.org/issues/21003
* Author: decuplet (Nikita Shilnikov)
* Status: Open
* ruby -v: ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +PRISM [arm64-darwin24]
* Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN
----------------------------------------
I stumbled upon this during the upgrade to 3.4. Here's the minimal repro:
```ruby
$VERBOSE = true
def foo(*, &block) = block
def bar(buz, ...) = foo(buz, ...)
bar(:test) {}
```
It gives
```
ruby reproduce.rb
reproduce.rb:6: warning: the block passed to 'Object#bar' defined at reproduce.rb:4 may be ignored
```
where I believe it shouldn't. No warning reported if I change `def bar(buz, ...)` to `def bar(...)`.
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/
next parent reply other threads:[~2025-01-04 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 13:41 decuplet (Nikita Shilnikov) via ruby-core [this message]
2025-01-05 0:17 ` [ruby-core:120481] " ydah (Yudai Takada) via ruby-core
2025-01-05 18:30 ` [ruby-core:120487] " kddnewton (Kevin Newton) via ruby-core
2025-02-14 1:51 ` [ruby-core:121004] " k0kubun (Takashi Kokubun) via ruby-core
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.issue-21003.20250104134116.8259@ruby-lang.org \
--to=ruby-core@ml.ruby-lang.org \
--cc=noreply@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).