Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

1
  • 6
    Don't extrapolate too much from the tone. The author is just talking about what role he wants the class/interface to play in the design, and what information he wants to communicate, vs what he doesn't. He's just saying it shouldn't matter to the client that it's an interface, only that it's a polymorphic type that satisfies some abstract behavior. "even if users know something none of their businesses, it seems also no harms for users" - well, when users know (or rather, rely on) something that's supposed to be an implementation detail, it can harm you, if you want to supply future versions. Commented Apr 19, 2024 at 22:55