Forum: Ruby-core [ruby-trunk - Feature #7418][Open] Kernel#used_refinements

Issue #7418 has been reported by charliesome (Charlie Somerville).

----------------------------------------
Feature #7418: Kernel#used_refinements
https://bugs.ruby-lang.org/issues/7418

Author: charliesome (Charlie Somerville)
Status: Open
Priority: Normal
Assignee:
Category:
Target version:


I'd like to propose a method that returns an array of all refinements 
visible from the current scope. I have documented the ordering of the 
return array as undefined to allow a bit of flexibility in how it is 
implemented across the various Ruby implementations.

One of the criticisms of refinements is that its use makes code harder 
to understand - especially when non-lexical refinements are being used. 
This method slightly improves the situation by making debugging of code 
using refinements easier.

I've named the method 'used_refinements' for now, but I'm open to 
changing that to something else.

I've already done the initial implementation which is attached as a 
patch. Feedback would be most appreciated.

Maybe it should be called Module.refinements (a la Module.nesting).

// Magnus Holm


On Wed, Nov 21, 2012 at 12:16 PM, charliesome (Charlie Somerville)

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

Status changed from Open to Assigned
Assignee set to shugo (Shugo Maeda)

judofyr (Magnus Holm) wrote:
> Maybe it should be called Module.refinements (a la Module.nesting).

Module.refinements conflicts with Module#refinements, which returns 
refinements defined in the receiver.

----------------------------------------
Feature #7418: Kernel#used_refinements
https://bugs.ruby-lang.org/issues/7418#change-33462

Author: charliesome (Charlie Somerville)
Status: Assigned
Priority: Normal
Assignee: shugo (Shugo Maeda)
Category:
Target version:


I'd like to propose a method that returns an array of all refinements 
visible from the current scope. I have documented the ordering of the 
return array as undefined to allow a bit of flexibility in how it is 
implemented across the various Ruby implementations.

One of the criticisms of refinements is that its use makes code harder 
to understand - especially when non-lexical refinements are being used. 
This method slightly improves the situation by making debugging of code 
using refinements easier.

I've named the method 'used_refinements' for now, but I'm open to 
changing that to something else.

I've already done the initial implementation which is attached as a 
patch. Feedback would be most appreciated.

Issue #7418 has been updated by mame (Yusuke Endoh).

Target version set to next minor

Shugo, is this feature mandatory for the 2.0.0 refinements?
I'm setting to next minor tentatively.

--
Yusuke Endoh <mame@tsg.ne.jp>
----------------------------------------
Feature #7418: Kernel#used_refinements
https://bugs.ruby-lang.org/issues/7418#change-33752

Author: charliesome (Charlie Somerville)
Status: Assigned
Priority: Normal
Assignee: shugo (Shugo Maeda)
Category:
Target version: next minor


I'd like to propose a method that returns an array of all refinements 
visible from the current scope. I have documented the ordering of the 
return array as undefined to allow a bit of flexibility in how it is 
implemented across the various Ruby implementations.

One of the criticisms of refinements is that its use makes code harder 
to understand - especially when non-lexical refinements are being used. 
This method slightly improves the situation by making debugging of code 
using refinements easier.

I've named the method 'used_refinements' for now, but I'm open to 
changing that to something else.

I've already done the initial implementation which is attached as a 
patch. Feedback would be most appreciated.