From: "osyo (manga osyo)" <noreply@ruby-lang.org>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:105799] [Ruby master Bug#18268] Behavior change when `each_cons` and `break ... if false` are combined in Ruby 3.1
Date: Tue, 26 Oct 2021 03:09:46 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-94317.20211026030946.9869@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-18268.20211026025517.9869@ruby-lang.org
Issue #18268 has been updated by osyo (manga osyo).
It appears to have been changed at https://github.com/ruby/ruby/pull/1509.
----------------------------------------
Bug #18268: Behavior change when `each_cons` and `break ... if false` are combined in Ruby 3.1
https://bugs.ruby-lang.org/issues/18268#change-94317
* Author: koic (Koichi ITO)
* Status: Open
* Priority: Normal
* ruby -v: ruby 3.1.0dev (2021-10-26T00:30:42Z master 7d4c59203f) [x86_64-darwin19]
* Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN
----------------------------------------
I'm not sure the details, but the following behavior has changed between Ruby 3.0.2 (and earlier) and Ruby 3.1.0-dev.
```ruby
# example.rb
def foo
[1, 2].each_cons(2) do |one, two|
break one if false
end
end
p foo
```
## Expected Behavior (Ruby 3.0.2)
It returns `nil`.
```console
% rbenv local 3.0.2
% ruby -v
ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-darwin19]
% ruby example.rb
nil
```
## Actual Behavior (Ruby 3.1.0-dev)
It returns `[1, 2]`.
```console
% rbenv local 3.1.0-dev
% ruby -v
ruby 3.1.0dev (2021-10-26T00:30:42Z master 7d4c59203f) [x86_64-darwin19]
% ruby example.rb
[1, 2]
```
I encountered this issue with the following RuboCop build error.
https://app.circleci.com/pipelines/github/rubocop/rubocop/5414/workflows/4a7e4b81-7380-41e5-8ede-e28d9160010d/jobs/201236
The code I encountered is below.
https://github.com/rubocop/rubocop/blob/v1.22.2/lib/rubocop/cop/layout/block_alignment.rb#L104-L106
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2021-10-26 3:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 2:55 [ruby-core:105798] [Ruby master Bug#18268] Behavior change when `each_cons` and `break ... if false` are combined in Ruby 3.1 koic (Koichi ITO)
2021-10-26 3:09 ` osyo (manga osyo) [this message]
2021-10-26 7:05 ` [ruby-core:105802] " koic (Koichi ITO)
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.journal-94317.20211026030946.9869@ruby-lang.org \
--to=ruby-core@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).