I’m happy to announce the first release of Inherit.jl . The package provides a simple way to inherit fields and interface definitions in Julia. it is currently available in the general registry (] add Inherit). Example: using Inherit " Base type of Fruity objects. Creates a julia native type with…

Is this (partially) redundant with many other OOP packages (there’s also OOPMacro.jl and CBOO something): [image] [ANN] ObjectOriented.jl (renamed from TyOOP.jl), complete OOP support Package Announcements Hi community! It has been quite a long time since my last post, an…

I’m not sure what you’re getting here that you don’t get from Mixers.jl, which is only 100 lines, and is independent from the inheritance mechanism.

Hey, guys, let’s keep it positive. First of all, congratulations on your package! Maybe, could you elaborate a bit more on the differences between your package and those mentioned? Thanks, and congrats again!

The main difference I can see is they don’t seem to verify method signatures. Their interface seems to be only checking for a function name? Found this post about ObjectOriented.jl [image] [ANN] ObjectOriented.jl (renamed from TyOOP.jl), complete OOP support Package Announcements …

Mixers.jl only inherit fields not interfaces.

Thanks. This has method signature verification. You can always dispatch to the signature you see.

Sorry to be negative, there are a lot of attempts at these packages and mostly they don’t end up being used. I don’t users Mixers.jl at all. The solution ends up being use composition 99% of the time. I also couldn’t understand how you were enforcing interface compatibility, but I see that its usin…

Nothing wrong with negative feedback when it contains valid points. Inheritance offers more natural, cleaner syntax than composition in many cases. It also naturally has zero dispatch overhead. It’s bad if not used well, but obviously no OOP package stops user from using composition. I wouldn’t us…

I like the look of this. Julia’s lack of enforcing interfaces is IMO one of its greatest obstacles to writing reliable code.

Init actually is run during precompilation :wink: Putting code in init means longer load times if all interfaces need verification. Imagine something complicated like AbstractArray. The interface idea is great (I had a go in Interfaces.jl) but Im not sure about runtime checks. You may as well do t…

Inherit.jl

Package Announcements

Palli May 19, 2023, 11:27am 2

Is this (partially) redundant with many other OOP packages (there’s also OOPMacro.jl and CBOO something):

Topic		Replies	Views
Inheritance in Julia New to Julia inheritance	11	15043	September 1, 2017
How do you inherit Interface? General Usage question	8	1572	April 2, 2018
About inheritance and abstract types New to Julia inheritance	46	10605	June 12, 2020
Workaround for traditional inheritance features in object-oriented languages General Usage inheritance , structtypes	40	10412	November 14, 2017
Method inheritance the Julian way New to Julia inheritance	18	2662	August 29, 2021

Inherit.jl

Related topics