# Interfaces/traits in julia 2.0 and multiple inheritance

**URL:** https://discourse.julialang.org/t/interfaces-traits-in-julia-2-0-and-multiple-inheritance/124011
**Category:** Internals & Design
**Tags:** traits, interface
**Created:** [December 20, 2024, 11:13am UTC](https://discourse.julialang.org/t/interfaces-traits-in-julia-2-0-and-multiple-inheritance/124011 "2024-12-20T11:13:51Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![Mason](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mason/32/2423_2.png) [@Mason](https://discourse.julialang.org/u/Mason)
#### Post date: [December 20, 2024, 12:16pm UTC](https://discourse.julialang.org/t/interfaces-traits-in-julia-2-0-and-multiple-inheritance/124011/4 "2024-12-20T12:16:40Z")

</div>

> [@jakobnissen](#):
>
> Broadly speaking, I agree that Julia’s inheritance model is not particularly good. Most of the interesting properties of types are not monophyletic.  
> But I do believe you’re underestimating the problem of ambiguity that would result from crossing Julian multiple dispatch with a trait system. I fear method ambiguities would explode.

For what it’s worth, we had this conversation already rather extensively in [Why did Julia choose nominal typing over structural typing/traits?](https://discourse.julialang.org/t/why-did-julia-choose-nominal-typing-over-structural-typing-traits/122517) and the response was more or less that the OP did not believe that this would actually be a problem. 🤷

---

_[View the full topic](https://discourse.julialang.org/t/interfaces-traits-in-julia-2-0-and-multiple-inheritance/124011)._