▲ 102 ▼ The Tragic Death of Inheritance (avivcarmi.com) submitted 3 years ago by snaggen@programming.dev to c/programming@programming.dev 52 comments fedilink hide all child comments
[–] dragontamer@lemmy.world 4 points 3 years ago (2 children) You're not describing composition. Go Files do not "hasa reader". You don't do file.reader.read(), you just do file.read(), that's inheritance as file has inherited the read() method. permalink fedilink source parent hideshow 4 child comments replies: [–] colonial@lemmy.world 8 points 3 years ago You're confusing polymorphism for inheritance. read is a method on an interface that File implements - it is not inherited from a base class. You can use that File directly, or wherever a Reader interface (or whatever the name is, idk I don't really do Go) is expected. permalink fedilink source parent [–] orangeboats@lemmy.world 4 points 3 years ago (1 child) Composition do not necessitate the creation of a new field like x.reader or x.writer, what are you on? permalink fedilink source parent hideshow 2 child comments replies: [–] dragontamer@lemmy.world 0 points 3 years ago (1 child) https://www.infoworld.com/article/3409071/java-challenger-7-debugging-java-inheritance.html#toc-2 composition is literally the "has a" relationship. That's how its always been taught. permalink fedilink source parent hideshow 2 child comments replies: [–] platypus_plumba@lemmy.world 1 point 3 years ago* (last edited 3 years ago) Man, I honestly have no idea why they are downvoting you. Composition literally means taking common behavior and placing it in external objects behind interfaces using a has-a relationship. No idea why they are denying this. Inheritance vs composition is the same as "is-a" vs "has-a". In composition re usability isn't done via inheritance but code encapsulation. Saying that in Go objects can implement many interfaces is the Interface Segregation principle from SOLID. Basically having small interfaces instead of a big interface with methods that may not be implemented by all implementors. permalink fedilink source parent
[–] colonial@lemmy.world 8 points 3 years ago You're confusing polymorphism for inheritance. read is a method on an interface that File implements - it is not inherited from a base class. You can use that File directly, or wherever a Reader interface (or whatever the name is, idk I don't really do Go) is expected. permalink fedilink source parent
[–] orangeboats@lemmy.world 4 points 3 years ago (1 child) Composition do not necessitate the creation of a new field like x.reader or x.writer, what are you on? permalink fedilink source parent hideshow 2 child comments replies: [–] dragontamer@lemmy.world 0 points 3 years ago (1 child) https://www.infoworld.com/article/3409071/java-challenger-7-debugging-java-inheritance.html#toc-2 composition is literally the "has a" relationship. That's how its always been taught. permalink fedilink source parent hideshow 2 child comments replies: [–] platypus_plumba@lemmy.world 1 point 3 years ago* (last edited 3 years ago) Man, I honestly have no idea why they are downvoting you. Composition literally means taking common behavior and placing it in external objects behind interfaces using a has-a relationship. No idea why they are denying this. Inheritance vs composition is the same as "is-a" vs "has-a". In composition re usability isn't done via inheritance but code encapsulation. Saying that in Go objects can implement many interfaces is the Interface Segregation principle from SOLID. Basically having small interfaces instead of a big interface with methods that may not be implemented by all implementors. permalink fedilink source parent
[–] dragontamer@lemmy.world 0 points 3 years ago (1 child) https://www.infoworld.com/article/3409071/java-challenger-7-debugging-java-inheritance.html#toc-2 composition is literally the "has a" relationship. That's how its always been taught. permalink fedilink source parent hideshow 2 child comments replies: [–] platypus_plumba@lemmy.world 1 point 3 years ago* (last edited 3 years ago) Man, I honestly have no idea why they are downvoting you. Composition literally means taking common behavior and placing it in external objects behind interfaces using a has-a relationship. No idea why they are denying this. Inheritance vs composition is the same as "is-a" vs "has-a". In composition re usability isn't done via inheritance but code encapsulation. Saying that in Go objects can implement many interfaces is the Interface Segregation principle from SOLID. Basically having small interfaces instead of a big interface with methods that may not be implemented by all implementors. permalink fedilink source parent
[–] platypus_plumba@lemmy.world 1 point 3 years ago* (last edited 3 years ago) Man, I honestly have no idea why they are downvoting you. Composition literally means taking common behavior and placing it in external objects behind interfaces using a has-a relationship. No idea why they are denying this. Inheritance vs composition is the same as "is-a" vs "has-a". In composition re usability isn't done via inheritance but code encapsulation. Saying that in Go objects can implement many interfaces is the Interface Segregation principle from SOLID. Basically having small interfaces instead of a big interface with methods that may not be implemented by all implementors. permalink fedilink source parent