Re: Simple example on interfaces

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On 2021-01-26 08:33, G.B. wrote:

> Composition can be a good alternative, too.

Composition was the starting point. See the original post.

> It can help making the type graph modular.

By modular by mean disconnected? But the question was to make it 
connected by removing duplicated nodes.

> It naturally adds separation of concerns.
> Is there good reason to prefer Is-A over Has-A?

It is not a question of preference, it either fallacy (when set in mixed 
with a member of) or else different interfaces, like record type 
interface vs. some other interface.

> If all the types are related through inheritance,
> will refactoring become easier or harder?

You meant reuse, probably. Composition was zero re-use beyond your 
editor's clipboard support of cut-and-paste.

As for logical relationships between types, usually such things are 
influenced by the problem space. The question of design to map these by 
language types.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de