From: ruby-core@... Date: 2016-08-24T12:21:01+00:00 Subject: [ruby-core:77039] [Ruby trunk Feature#12697] Why shouldn't Module meta programming methods be public? Issue #12697 has been updated by Marc-Andre Lafortune. Assignee set to Yukihiro Matsumoto I made the same proposal years ago (#6539), and Matz stated that he ["thinks class/module operations should be done in the scope"](https://bugs.ruby-lang.org/issues/6539#note-3). I still strongly believe that `include` should be public, so I'll keep this open in case we manage to rally Matz ---------------------------------------- Feature #12697: Why shouldn't Module meta programming methods be public? https://bugs.ruby-lang.org/issues/12697#change-60264 * Author: bug hit * Status: Open * Priority: Normal * Assignee: Yukihiro Matsumoto ---------------------------------------- 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: