Issue #12697 has been updated by marcandre (Marc-Andre Lafortune).

Status changed from Feedback to Closed

shyouhei (Shyouhei Urabe) wrote:
> [...]We referred issue #6539 and now we remember that each method (not the "Module meta programming" at once) should have separate considerations.

Module#include is now public (yay :-) ) so I'm closing this.

I'll create separate issues for the others.

----------------------------------------
Feature #12697: Why shouldn't Module meta programming methods be public?
https://bugs.ruby-lang.org/issues/12697#change-67945

* Author: bughit (bug hit)
* Status: Closed
* Priority: Normal
* Assignee: matz (Yukihiro Matsumoto)
* Target version: 
----------------------------------------
Methods like alias_method, attr_accessor, define_method, and similar

I don't think Ruby discourages this kind of meta programming, so why make it less convenient, by necessitating `send` or `module_eval`?



-- 
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>