extended objects do not work like objects of module included classes about equalizer HOT 3 CLOSED

Nak from my side.

I only want the equalizer functionnalities for some objects, not all object of a class, so I define the equalizer like this:

Make a specific subclass where you include the Equalizer, and all objects you want to be equalized instances of that equalized subclass. Using Object#extend this way is IMO just hiding a design smell.

from equalizer.

@phurni Extending an object at runtime actually wipes our your entire global method cache. The performance impact of this technique is one of the reasons that DCI quickly fell out of favour in the ruby community a few years ago.

If you really must do it conditionally, I would suggest creating proxy objects that use Equalizer, and wrap your own objects in them and use those for equality testing.

from equalizer.

Yes, wrapping them was my first design. Then, because the number of objects could have been high, I tried to avoid the wrapping to reduce the performance hit. This was a faulty pre-optimization decision of my own.
Thanx for the reminder.

from equalizer.