ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "esad (Esad Hajdarevic) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "esad (Esad Hajdarevic)" <noreply@ruby-lang.org>
Subject: [ruby-core:117646] [Ruby master Bug#20444] Kernel#loop: returning the "result" value of StopIteration doesn't work when raised directly
Date: Mon, 22 Apr 2024 21:41:20 +0000 (UTC)	[thread overview]
Message-ID: <redmine.issue-20444.20240422214119.53307@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-20444.20240422214119.53307@ruby-lang.org

Issue #20444 has been reported by esad (Esad Hajdarevic).

----------------------------------------
Bug #20444: Kernel#loop: returning the "result" value of StopIteration doesn't work when raised directly
https://bugs.ruby-lang.org/issues/20444

* Author: esad (Esad Hajdarevic)
* Status: Open
* ruby -v: ruby 3.3.0 (2023-12-25 revision 5124f9ac75) [arm64-darwin20]
* Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN
----------------------------------------
There was a https://bugs.ruby-lang.org/issues/11498 a while ago which was merged in, but I was surprised to find out that raising `StopIteration` in a loop like

`loop { raise StopIteration.new(3) }`

returns nil and not 3.





-- 
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/postorius/lists/ruby-core.ml.ruby-lang.org/

       reply	other threads:[~2024-04-22 21:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 21:41 esad (Esad Hajdarevic) via ruby-core [this message]
2024-04-23  5:02 ` [ruby-core:117649] [Ruby master Bug#20444] Kernel#loop: returning the "result" value of StopIteration doesn't work when raised directly nobu (Nobuyoshi Nakada) via ruby-core
2024-04-23  6:21 ` [ruby-core:117650] " esad (Esad Hajdarevic) via ruby-core
2024-04-24  2:40 ` [ruby-core:117667] " nobu (Nobuyoshi Nakada) via ruby-core
2024-04-24  9:07 ` [ruby-core:117673] [Ruby master Feature#20444] " esad (Esad Hajdarevic) via ruby-core
2024-04-24 10:40 ` [ruby-core:117678] " ufuk (Ufuk Kayserilioglu) via ruby-core
2024-04-24 11:00 ` [ruby-core:117679] " esad (Esad Hajdarevic) via ruby-core
2024-04-26  8:28 ` [ruby-core:117722] " nobu (Nobuyoshi Nakada) via ruby-core
2024-04-26 10:07 ` [ruby-core:117726] " esad (Esad Hajdarevic) 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-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.issue-20444.20240422214119.53307@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    --cc=noreply@ruby-lang.org \
    --cc=ruby-core@ml.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 read-only IMAP folder(s) and NNTP newsgroup(s).