You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am considering adding the method alias_class_method to the Module class. However, it seems wasteful to have to add a special method for this, just as it seems wasteful for similar methods like class_accessor. We end up with a bunch of methods that are nothing more then copies of methods that already exist, but acting on the singleton class instead.
Facets has Kernel#eigen which can be used like so:
Not sure I like the eigen name. It used to be called meta but that seemed way too generic. But the question is: Is eigen a better approach? Or should we just be happy with a bunch of extra module methods? Or should we just support both?
The text was updated successfully, but these errors were encountered:
I prefer the first, its semantic is clear for me, although you chose a good name, it still is only a name, I feel it does not enough "work" to justify its existence.
Just my 2c.
BTW
Nice to know about the origin of eigen.
I am considering adding the method
alias_class_method
to the Module class. However, it seems wasteful to have to add a special method for this, just as it seems wasteful for similar methods likeclass_accessor
. We end up with a bunch of methods that are nothing more then copies of methods that already exist, but acting on the singleton class instead.Facets has
Kernel#eigen
which can be used like so:Not sure I like the
eigen
name. It used to be calledmeta
but that seemed way too generic. But the question is: Iseigen
a better approach? Or should we just be happy with a bunch of extra module methods? Or should we just support both?The text was updated successfully, but these errors were encountered: