Conversation

Olivier Halligon

@aligatr

·

Feb 26, 2015

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

@andy_matuschak

1

4

Olivier Halligon

@aligatr

·

Feb 26, 2015

@andy_matuschak

A code snippet being better than a thousand words: https://gist.github.com/AliSoftware/9e4946c8b6038572d678#file-struct_and_inherit-swift… so what's the best approach?

1

3

Andy Matuschak

@andy_matuschak

·

Feb 26, 2015

@aligatr

Composition.

1

1

LSB

@luisobo

·

Feb 26, 2015

@andy_matuschak

@aligatr

what if structs allowed inheritance?

1

Andy Matuschak

@andy_matuschak

·

Feb 26, 2015

@luisobo

@aligatr

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

1

2

LSB

@luisobo

·

Feb 26, 2015

@andy_matuschak

@aligatr

what are your concerns with method inheritance?

1

1

Andy Matuschak

@andy_matuschak

Replying to

@luisobo

@luisobo

@aligatr

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

3:53 PM · Feb 26, 2015·Twitter for Mac

Olivier Halligon

@aligatr

·

Feb 26, 2015

Replying to

@andy_matuschak

@andy_matuschak

@luisobo

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

1

Andy Matuschak

@andy_matuschak

·

Feb 26, 2015

@aligatr

@luisobo

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

1

Show replies