Conversation

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

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

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.

I get it, but it feels like exposing implementation details somehow… sometimes it's OK for model structs but still…

Replying to

It's not implementation details if the struct contains no implementation. It's just data.

7:07 PM · Feb 26, 2015Twitter for Mac

Replying to

True dat. That's actually how I already did it so far, but you convinced me to keep it that way then :)