From: Joseph Jones <joeyi5216@gmail.com>
To: Ruby developers <ruby-core@ruby-lang.org>
Cc: <ruby-core@ruby-lang.org>
Subject: [ruby-core:72343] [Ruby trunk - Bug #11779] [Open] Mudule#using does not make sense as a method
Date: Thu, 17 Dec 2015 21:13:23 -0700 [thread overview]
Message-ID: <AFC126BA-8859-4575-B92A-C372847D0176@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
Joseph Jones liked your message with Boxer. On December 6, 2015 at 14:40:14 MST, alxtskrnk@gmail.com wrote:Issue #11779 has been reported by bug hit.----------------------------------------Bug #11779: Mudule#using does not make sense as a methodhttps://bugs.ruby-lang.org/issues/11779* Author: bug hit* Status: Open* Priority: Normal* Assignee: * ruby -v: 2.2.3* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN----------------------------------------1. it can't be called from another method2. the receiver must be self3. since refinements are lexically scoped the self receiver must match the currently open class#3 is particularly curious```rubymodule Refinement refine String do def refined? true end endendmodule Foo def self.refined? ''.refined? rescue false endendmodule Bar def self.refined? ''.refined? rescue false end Foo.module_eval do using Refinement endendp Foo.refined? #false```The module_eval `#using` call does not raise (it's not from a method and the receiver is self), but evidently because currently open class does not match self, it does not do anything. So it should at least raise.So `#using`, though a method, does not function as a method, which is misleading.-- https://bugs.ruby-lang.org/
[-- Attachment #2: Type: text/html, Size: 1829 bytes --]
reply other threads:[~2015-12-18 3:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=AFC126BA-8859-4575-B92A-C372847D0176@gmail.com \
--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).