# Overloading f(x) call syntax with \`call\` generic

**URL:** <https://discourse.julialang.org/t/overloading-f-x-call-syntax-with-call-generic/874>\
**Category:** Internals & Design\
**Tags:** question\
**Created:** [December 11, 2016, 11:57pm UTC](https://discourse.julialang.org/t/overloading-f-x-call-syntax-with-call-generic/874 "2016-12-11T23:57:51Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![martinholters](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/martinholters/32/3690_2.png) [@martinholters](https://discourse.julialang.org/u/martinholters)\
**Post date:** [January 6, 2017, 9:06am UTC](https://discourse.julialang.org/t/overloading-f-x-call-syntax-with-call-generic/874/21 "2017-01-06T09:06:16Z")

</div>

Note the relation to  
[https://github.com/JuliaLang/julia/issues/14919](https://github.com/JuliaLang/julia/issues/14919)  
as fixing that would allow

```julia
(f::Any)(a,b,c) = ...

```

to be used like what `call(f, a, b, c) = ....` is intended to do, except this might not intercept all calls, but could participate in normal dispatch, so that `foo(a,b,c)=...` would be more specific. Hm, but then defining `(f::Any)(a::Placeholder)` and `foo(a::Any)` would lead to an ambiguity when trying to call `foo(::Placeholder)`. So that issue is related, but maybe not the solution here.

[Previous page](https://discourse.julialang.org/t/overloading-f-x-call-syntax-with-call-generic/874.md?page=1)
