From: usa@garbagecollect.jp
To: ruby-core@ruby-lang.org
Subject: [ruby-core:103223] [Ruby master Bug#17533] Named capture is not assigned to the same variable as reserved words.
Date: Sun, 04 Apr 2021 23:44:17 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-91301.20210404234416.4@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-17533.20210113121446.4@ruby-lang.org
Issue #17533 has been updated by usa (Usaku NAKAMURA).
Backport changed from 2.5: REQUIRED, 2.6: REQUIRED, 2.7: DONE, 3.0: DONE to 2.5: REQUIRED, 2.6: DONE, 2.7: DONE, 3.0: DONE
backported into ruby_2_6 at r67927
----------------------------------------
Bug #17533: Named capture is not assigned to the same variable as reserved words.
https://bugs.ruby-lang.org/issues/17533#change-91301
* Author: nobu (Nobuyoshi Nakada)
* Status: Closed
* Priority: Normal
* Backport: 2.5: REQUIRED, 2.6: DONE, 2.7: DONE, 3.0: DONE
----------------------------------------
It is expected that named captures don't add new variables same as reserved words, and such variables couldn't be made usually at the time when named capture was implemented.
Keyword arguments since 2.0 can be the same as reserved words, however an assignment to an such already defined variable has been also suppressed now.
```ruby
def test(s, nil: :ng)
/(?<nil>.)/ =~ s
binding.local_variable_get(:nil)
end
p test("a") #=> :ng
```
```ruby
tap do |nil: :ng|
/(?<nil>.)/ =~ "c"
p binding.local_variable_get(:nil) #=> :ng
end
```
--
https://bugs.ruby-lang.org/
prev parent reply other threads:[~2021-04-04 23:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 12:14 [ruby-core:102060] [Ruby master Bug#17533] Named capture is not assigned to the same variable as reserved words nobu
2021-02-01 12:35 ` [ruby-core:102354] " naruse
2021-04-04 23:44 ` usa [this message]
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-91301.20210404234416.4@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).