# Function name conflict: ADL / function merging?

**URL:** <https://discourse.julialang.org/t/function-name-conflict-adl-function-merging/10335>\
**Category:** Internals & Design\
**Tags:** proposal, namespaces\
**Created:** [April 14, 2018, 5:16pm UTC](https://discourse.julialang.org/t/function-name-conflict-adl-function-merging/10335 "2018-04-14T17:16:17Z")\
**Posts on this page:** 1\
**Showing post:** 197

<div class="post-metadata">

**Author:** ![tkoolen](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkoolen/32/1603_2.png) [@tkoolen](https://discourse.julialang.org/u/tkoolen)\
**Post date:** [April 20, 2018, 8:52pm UTC](https://discourse.julialang.org/t/function-name-conflict-adl-function-merging/10335/197 "2018-04-20T20:52:15Z")

</div>

> [@jeff.bezanson](#):
>
> Just to make sure I understand: if C++ had an Any type, and XModule contained f(x::Any), the call f(x) somewhere else (in a module that doesn’t import XModule) could not call that method?

Exactly.

> [@jeff.bezanson](#):
>
> Julia method applicability is based on subtyping, and not on something like whether a definition “mentions” a certain type.

Is that really different from C++'s templated functions and template specializations though? C++ makes ADL work for these. In fact, Sutter’s ‘modest proposal’ PDF from [my earlier comment](https://discourse.julialang.org/t/function-name-conflict/10335/190) addressed exactly the issue that C++ used to be too liberal in applying ADL in the face of templated functions.

---

_[View the full topic](https://discourse.julialang.org/t/function-name-conflict-adl-function-merging/10335)._
