Does using interfaces extensively have a performance drawback like using 
inheritance has?

Why do I ask? I was thinking about adopting a coding practice where I define 
explicit interfaces for all public aspects of my classes, and then couples the 
interfaces closely to unit tests. Then, whenever I would create a new class 
using some of these interfaces the unit tests would tag along, which means the 
unit tests would be reusable.

Now, if the compiler has do align stuff in some arduous way to accommodate 
these interfaces then this whole idea might not be worth it? Or are interfaces 
a no-cost constraint on the implementation?

Erik Meer

Reply via email to