[ruby-core:105856] [Ruby master Feature#11919] Passing a module directly

Issue #11919 has been updated by jeremyevans0 (Jeremy Evans).

Status changed from Feedback to Rejected

Eregon (Benoit Daloze) wrote in #note-8:
> I guess we need to persuade matz then: https://bugs.ruby-lang.org/issues/14344#note-15 (https://bugs.ruby-lang.org/issues/16241#note-5 has some more context)

This shows why we need feature triaging.  Otherwise developers who are trying to contribute end up working on things that have already been rejected.  I'll reject this and close the related pull request.

----------------------------------------
Feature #11919: Passing a module directly 
https://bugs.ruby-lang.org/issues/11919#change-94394

* Author: sawa (Tsuyoshi Sawada)
* Status: Rejected
* Priority: Normal
----------------------------------------
Refinement requires a named module:

~~~ruby
module MyRefinement
  refine ...
  ...
end

using MyRefinement
~~~

but often (but not always), refinements are called by the `using` command only in once in a single file, and should not need to be named in such case. Also, the purpose of refinement is to not pollute classes with methods. Necessity to define a module and polluting the name space looks to me to go against this idea.

I would like to do:

~~~ruby
using Module.new do
  refine ...
  ...
end
~~~




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

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