Feature #19714
closed
I am not 100% satisfied. Probably (unlike class_eval
and module_eval
whose class/module distinction is for the receiver), the method returns a class or a module, unrelated to the name.
Is there any idea?
Matz.
matz (Yukihiro Matsumoto) wrote in #note-2:
I am not 100% satisfied. Probably (unlike class_eval
and module_eval
whose class/module distinction is for the receiver), the method returns a class or a module, unrelated to the name.
Is there any idea?
#refined_target
#refined_subject
#refined_receiver
#refined_context
The first one I came up with is #refined_subject
in the same sense as #subject
in RSpec: http://rspec.info/features/3-12/rspec-core/subject/explicit-subject/
Among those proposed names, target
and subject
are acceptable. I am not sure refined_
prefix required or not, as not being English native.
Maybe should we admit the design mistake and make refined_class
obsolete?
Matz.
matz (Yukihiro Matsumoto) wrote in #note-4:
Among those proposed names, target
and subject
are acceptable. I am not sure refined_
prefix required or not, as not being English native.
Maybe should we admit the design mistake and make refined_class
obsolete?
I prefer target
and agree to making refined_class
obsolete.
Make obsolete = deprecate it, right? (sounds OK)
Refinement#target
sounds good to me.
- Status changed from Assigned to Closed
- Related to Feature #19366: Rename/alias Refinedment#refined_class => #refined_module added
- Related to Feature #20901: What's status of Refinement#refined_class? added
Also available in: Atom
PDF
Like0
Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0