From: XrXr@users.noreply.github.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:94333] [Ruby master Bug#16097] [PATCH] Don't accidentally name anonymous module/class
Date: Wed, 14 Aug 2019 01:23:44 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-80725.20190814012344.389b36d93ccfd26e@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16097.20190811154014@ruby-lang.org
Issue #16097 has been updated by alanwu (Alan Wu).
Done. The [latest commit](https://github.com/ruby/ruby/pull/2337/commits/36e00760a42a09266521fc503a0bda7af632a4e3) has a reference to this ticket.
----------------------------------------
Bug #16097: [PATCH] Don't accidentally name anonymous module/class
https://bugs.ruby-lang.org/issues/16097#change-80725
* Author: alanwu (Alan Wu)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v:
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
My patch in #15765 accidentally introduced a behavior change.
`ruby -ve 'Module.new { class self::A; end; p name }'` outputs a name
similar to `Module#inspect` when it should output `nil` like in Ruby 2.6.x.
I have a pull request to fix this: https://github.com/ruby/ruby/pull/2337
--
https://bugs.ruby-lang.org/
prev parent reply other threads:[~2019-08-14 1:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-16097.20190811154014@ruby-lang.org>
2019-08-11 15:40 ` [ruby-core:94277] [Ruby master Bug#16097] [PATCH] Don't accidentally name anonymous module/class XrXr
2019-08-13 23:48 ` [ruby-core:94330] " nobu
2019-08-14 1:23 ` XrXr [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-80725.20190814012344.389b36d93ccfd26e@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).