But if I have to make an Array I have to inherit from Indexable which inherits from Collection which inherits from Object! How else am I supposed to implement an Array?

[–] SparroHawc@lemmy.zip 4 points 1 day ago* (last edited 1 day ago) (1 children)

Admittedly this is why I like C#'s 'implements' paradigm. Doesn't have to inherit, it just has to fulfill the contract, and then you can pass it to anything that expects the interface it implements. Keeps you from building giant trees.

[–] calcopiritus@lemmy.world 3 points 22 hours ago (1 children)

As a rust developer I feel obligated by religion to make this comment:

Then you'd love rust! Rust only has "interfaces" (called traits) but doesn't have inheritance. You just have traits that don't inherit from anything and structs (that don't inherit from other structs) that implement X amount of traits.

So you can have the good things about OOP without the bad ones.

And these traits allow you to make trait objects, which would be like regular objects in C# (with vtables for the methods). If 2 different structs implement the same trait, you can "downcast" them to a trait object and store them in the same array. Or pass it is an argument to a function that wants something that implements that trait but doesn't care about the specific struct. You can of course cast it back later to the original struct.

[–] SparroHawc@lemmy.zip 2 points 10 hours ago

I like interfaces as a supplement to inheritance. The strength of inheritance is getting all of the internal functionality of the parent class, while still allowing you to differentiate between children.

Interfaces are useful for disparate classes which don't have much in common besides fitting within a specific use case, rather than classes that are very similar to each other but need specific distinguishing features.

[–] mesamunefire@piefed.social 2 points 2 days ago

I remember some crazy stuff back when I had to work with a Java + ember.js project. Everything was like that.