From: ruby-core@... Date: 2017-11-28T02:24:43+00:00 Subject: [ruby-core:83899] [Ruby trunk Feature#12697][Closed] Why shouldn't Module meta programming methods be public? 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: