From: shyouhei@... Date: 2016-11-25T13:46:37+00:00 Subject: [ruby-core:78362] [Ruby trunk Feature#12697] Why shouldn't Module meta programming methods be public? Issue #12697 has been updated by Shyouhei Urabe. We looked at this issue at todays developer meeting. We referred issue #6539 and now we remember that each method (not the "Module meta programming" at once) should have separate considerations. While Matz do not like `String.include Term::ANSIColor`, other methods still have chance. ---------------------------------------- Feature #12697: Why shouldn't Module meta programming methods be public? https://bugs.ruby-lang.org/issues/12697#change-61727 * Author: bug hit * Status: Feedback * 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: