Leaky abstraction by omission
Leaky abstraction by omission
An example of Leaky Abstraction where a code interface inadvertently exposes implementation details through inconsistent design.
Mark Seeman gives an example of an interface where some methods require a specific argument, while others don't - because one particular implementation doesn't need that information.