Issue #14744 has been updated by shugo (Shugo Maeda).

Assignee set to matz (Yukihiro Matsumoto)

> So the refinement module (self in the refine Array do block) is a Module, but looking at its ancestors it has Array as a "superclass".
> 
> Is that expected?

The superclass of a refinement module is for implementing super in refined methods.
However, it may be better to hidden from reflection APIs.

What do you think, Matz?



----------------------------------------
Bug #14744: Refinements modules have a superclass
https://bugs.ruby-lang.org/issues/14744#change-71916

* Author: Eregon (Benoit Daloze)
* Status: Open
* Priority: Normal
* Assignee: matz (Yukihiro Matsumoto)
* Target version: 
* ruby -v: ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux]
* Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
~~~
$ ruby -e 'module M; refine Array do; p self; p self.class; p ancestors; end; end'
#<refinement:Array@M>
Module
[#<refinement:Array@M>, Array, Enumerable, Object, Kernel, BasicObject]
~~~

So the refinement module (self in the `refine Array do` block) is a Module, but looking at its ancestors it has Array as a "superclass".

Is that expected?
I thought modules can never have a superclass in Ruby.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>