[ruby-core:105326] [Ruby master Bug#17429] Prohibit include/prepend in refinement modules

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


shugo (Shugo Maeda) wrote in #note-31:
> mame (Yusuke Endoh) wrote in #note-30:
> > BTW, the change seems to add a top-level new constant `::Refinement`. I'm not against the addition, but unsure about the impact. Is it okay?
> 
> I found a gem named refinement....
> 
> https://github.com/square/refinement/blob/master/lib/refinement.rb

I've created an issue on the project: <https://github.com/square/refinement/issues/71>.

By gem-codesearch, I've found another gem which defines ::Refinement.

* https://github.com/rkh/refine/blob/master/lib/refine.rb

However, it's a gem for very old Ruby versions without Refinements, so I believe there's no problem.


----------------------------------------
Bug #17429: Prohibit include/prepend in refinement modules
https://bugs.ruby-lang.org/issues/17429#change-93740

* Author: shugo (Shugo Maeda)
* Status: Open
* Priority: Normal
* Assignee: matz (Yukihiro Matsumoto)
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
include/prepend in refinement modules has implementation difficulties such as #17007 and #17379, and tends to be misleading like #17374.
How about to prohibit it in future versions?

Method copy like #17380 may be more convenient, but it's confusing to use names include and prepend because semantics is different from the original ones.




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

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