# Claim (false): Julia isn't multiple dispatch but overloading

**URL:** <https://discourse.julialang.org/t/claim-false-julia-isnt-multiple-dispatch-but-overloading/42370>\
**Category:** General Usage\
**Tags:** multidispatch\
**Created:** [July 1, 2020, 1:55pm UTC](https://discourse.julialang.org/t/claim-false-julia-isnt-multiple-dispatch-but-overloading/42370 "2020-07-01T13:55:00Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![dataSurfer](https://avatars.discourse-cdn.com/v4/letter/d/67e7ee/32.png) [@dataSurfer](https://discourse.julialang.org/u/dataSurfer)\
**Post date:** [July 1, 2020, 2:32pm UTC](https://discourse.julialang.org/t/claim-false-julia-isnt-multiple-dispatch-but-overloading/42370/13 "2020-07-01T14:32:26Z")

</div>

> [@lungben](#):
>
> Here is a great illustration of an other aspect of multiple dispatch vs. function overloading (in addition to the good example of @Maurizio_Tomasi) .
> 
> [Julia Basics: Multiple Dispatch](https://opensourc.es/blog/basics-multiple-dispatch/#wait_what_about_function_overloading_in_c)

What I’m saying is that this is **not** multiple dispatch, it’s function overloading. All you are doing is limiting the types the function _meet_ can call by forcing them to be in a specific type range. You can do that in C++ and D. The resolution itself occurs at compile time.

---

_[View the full topic](https://discourse.julialang.org/t/claim-false-julia-isnt-multiple-dispatch-but-overloading/42370)._