Conversation

In #swiftlang if our model are struct but we need inheritance, is it better to migrate to classes or to use composition?

@andy_matuschak

A code snippet being better than a thousand words: gist.github.com/AliSoftware/9e so what's the best approach?

Composition.

what if structs allowed inheritance?

Some languages do have that. Field inheritance maybe useful; don't like method inheritance.

what are your concerns with method inheritance?

Depends somewhat on context but in general, child implementations create tight couplings, often to inexplicit semantics.

Thx for your insight. So in my GIST (updated) the best approach is solution 3 right? to still keep encapsulation

Replying to

I often literally do struct CarData { let vehicleData: VehicleData […] }

6:17 PM · Feb 26, 2015Twitter for Mac

Replying to

So my solution 2… doesn't it bother you that it exposes the inheritance and you need to use car.vehicle.model then?

Not really, no, but maybe because I think of this stuff more in terms of math and sets than in terms of simulation.

Show replies