ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "ydah (Yudai Takada) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "ydah (Yudai Takada)" <noreply@ruby-lang.org>
Subject: [ruby-core:120480] [Ruby master Bug#21001] unexpected nil result from proc with ensure and next
Date: Sun, 05 Jan 2025 00:14:57 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-111264.20250105001456.55456@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-21001.20250103201014.55456@ruby-lang.org>

Issue #21001 has been updated by ydah (Yudai Takada).


Note) This does not occur even in Ruby 3.4.1 when `--parser=parse.y`.

```
❯ ruby --parser=parse.y -e 'puts "Ruby: #{RUBY_VERSION}"

# okay all versions
# RUN_ARRAY = [1]

# fails ruby 3.4 only
RUN_ARRAY = [1,2]

MAP_PROC = Proc.new do |&blk|
  block_results = []
  RUN_ARRAY.each do |value|
    block_value = blk.call(value)
    block_results.push block_value
  end
  block_results
ensure
  next block_results
end

test_fn_results = MAP_PROC.call do |value|
  break if value > 1
  next value
end

puts test_fn_results.inspect'
Ruby: 3.4.1
[1]
```

----------------------------------------
Bug #21001: unexpected nil result from proc with ensure and next
https://bugs.ruby-lang.org/issues/21001#change-111264

* Author: aharpervc (Andrew Harper)
* Status: Open
* ruby -v: ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +PRISM [x86_64-linux]
* Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN
----------------------------------------
Hello,

I have noticed a different program behavior in Ruby 3.4 compared to previous versions. This is a simplified example for debugging that returns the expected result in Ruby 3.3 but nil in Ruby 3.4

Here is the example program:

``` ruby
puts "Ruby: #{RUBY_VERSION}"

# okay all versions
# RUN_ARRAY = [1]

# fails ruby 3.4 only
RUN_ARRAY = [1,2]

MAP_PROC = Proc.new do |&blk|
  block_results = []
  RUN_ARRAY.each do |value|
    block_value = blk.call(value)
    block_results.push block_value
  end
  block_results
ensure
  next block_results
end

test_fn_results = MAP_PROC.call do |value|
  break if value > 1
  next value
end

puts test_fn_results.inspect

```

For Ruby 3.3.6 the output is:

```
Ruby: 3.3.6
[1]
```

For Ruby 3.4.1 the output is:

```
Ruby: 3.4.1
nil
```

I am expecting the Ruby 3.3 output even for Ruby 3.4. This appears to be a bug, since the program implementation is unchanged. Perhaps there is a bug in the code that is now only showing up with Ruby 3.4, but that seemed unlikely since it's working as expected in other versions.

Thank you



-- 
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/

  reply	other threads:[~2025-01-05  0:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-03 20:10 [ruby-core:120472] " aharpervc (Andrew Harper) via ruby-core
2025-01-05  0:14 ` ydah (Yudai Takada) via ruby-core [this message]
2025-01-06  0:57 ` [ruby-core:120491] " kddnewton (Kevin Newton) via ruby-core
2025-02-14  1:52 ` [ruby-core:121006] " 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.journal-111264.20250105001456.55456@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).