From: ko1@atdot.net
To: ruby-core@ruby-lang.org
Subject: [ruby-core:69517] [Ruby trunk - Bug #11246] refine block doesn't respect "lexical" refinement information
Date: Wed, 10 Jun 2015 16:25:02 +0000 [thread overview]
Message-ID: <redmine.journal-52823.20150610162502.0be4526654e5160c@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11246.20150610162412@ruby-lang.org
Issue #11246 has been updated by Koichi Sasada.
Description updated
----------------------------------------
Bug #11246: refine block doesn't respect "lexical" refinement information
https://bugs.ruby-lang.org/issues/11246#change-52823
* Author: Koichi Sasada
* Status: Open
* Priority: Normal
* Assignee: Shugo Maeda
* ruby -v: ruby 2.3dev
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
The following program making two refinements refine class C.
```ruby
class C
def foo
p C
end
end
module R1
refine C do
def foo
p R1
super
end
end
end
using R1 # 1
module R2
using R1 # 2
refine C do
# using R1 # 3
def bar
C.new.foo
end
end
end
using R2
C.new.bar
```
Without `using R1 # 3`, `C#foo` was called in `R2::C#bar`.
By `using R1 #1` and `#2`, we declared that this lexical scope should use R1. However, it seems that this declaration is ignored.
Is it an intentional behavior?
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2015-06-10 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-11246.20150610162412@ruby-lang.org>
2015-06-10 16:24 ` [ruby-core:69516] [Ruby trunk - Bug #11246] [Open] refine block doesn't respect "lexical" refinement information ko1
2015-06-10 16:25 ` ko1 [this message]
2015-06-24 6:02 ` [ruby-core:69723] [Ruby trunk - Bug #11246] [Rejected] " shugo
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-52823.20150610162502.0be4526654e5160c@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).