# Named parameters with type overloads

**URL:** <https://discourse.julialang.org/t/named-parameters-with-type-overloads/18860>\
**Category:** General Usage\
**Created:** [December 20, 2018, 5:41pm UTC](https://discourse.julialang.org/t/named-parameters-with-type-overloads/18860 "2018-12-20T17:41:01Z")\
**Posts on this page:** 1\
**Showing post:** 33

<div class="post-metadata">

**Author:** ![Benny](https://avatars.discourse-cdn.com/v4/letter/b/49beb7/32.png) [@Benny](https://discourse.julialang.org/u/Benny)\
**Post date:** [February 29, 2024, 10:41am UTC](https://discourse.julialang.org/t/named-parameters-with-type-overloads/18860/33 "2024-02-29T10:41:26Z")

</div>

> [@Naming positional arguments at call site](https://discourse.julialang.org/t/naming-positional-arguments-at-call-site/103526/118):
>
> > [@Naming positional arguments at call site](https://discourse.julialang.org/t/naming-positional-arguments-at-call-site/103526/118):
> >
> > ```julia
> > function foo2(p1::Dog, p2::Cat)
> > function foo2(p2::Cat, p1::Dog)
> > 
> > ```
> 
> Same as
> 
> ```julia
> function foo2(p1::Dog, p2::Cat)
> function foo2(p2::Dog, p1::Cat)
> 
> ```
> 
> currently creates ambiguity for positional arguments but I don’t hear people complaining.

Those aren’t the same. My example had 2 methods, you changed it to 1 replaced method. You might benefit from reviewing the [documentation on methods](https://docs.julialang.org/en/v1/manual/methods/) and running code in the REPL to understand and verify the behavior.

> [@govorunov](#):
>
> Methods are not ‘overwritten’ but hidden.

Yes they are, the warning for method overwriting literally says it. The more serious issue there is the quoted excerpt was clearly denoted as a hypothetical language that is not Julia.

---

_[View the full topic](https://discourse.julialang.org/t/named-parameters-with-type-overloads/18860)._
