# About inheritance and abstract types

**URL:** <https://discourse.julialang.org/t/about-inheritance-and-abstract-types/5801>\
**Category:** New to Julia\
**Tags:** inheritance\
**Created:** [September 9, 2017, 5:28pm UTC](https://discourse.julialang.org/t/about-inheritance-and-abstract-types/5801 "2017-09-09T17:28:13Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![WschW](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/wschw/32/6575_2.png) [@WschW](https://discourse.julialang.org/u/WschW)\
**Post date:** [June 12, 2020, 3:18am UTC](https://discourse.julialang.org/t/about-inheritance-and-abstract-types/5801/15 "2020-06-12T03:18:45Z")

</div>

There are quite a few of those out there, many are listed in this thread:

> [@Composition and inheritance: the Julian way](https://discourse.julialang.org/t/composition-and-inheritance-the-julian-way/11231/80):
>
> Both @forward and @quasiabstract allow to implement reusing patterns. But what is the best pattern depends on the problem and the boundary conditions (i.e. if Alice and Bob talks to each other…). Hence it makes sense to provide them in a single package to facilitate switch back and forth, and to provide a clear comparison of the approaches in the examples. AFAIK, the @forward macro in ReusePatterns.jl is the only one which automatically forwads all the necessary methods. I’m not sure you …

---

_[View the full topic](https://discourse.julialang.org/t/about-inheritance-and-abstract-types/5801)._