# Type stability when arguments are functions

**URL:** <https://discourse.julialang.org/t/type-stability-when-arguments-are-functions/4734>\
**Category:** General Usage\
**Created:** [July 8, 2017, 12:16am UTC](https://discourse.julialang.org/t/type-stability-when-arguments-are-functions/4734 "2017-07-08T00:16:29Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![nalimilan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nalimilan/32/147_2.png) [@nalimilan](https://discourse.julialang.org/u/nalimilan)\
**Post date:** [July 8, 2017, 10:29am UTC](https://discourse.julialang.org/t/type-stability-when-arguments-are-functions/4734/3 "2017-07-08T10:29:44Z")

</div>

You could replace `fs::Vector{Function}` with `fs::Tuple{Vararg{Function}` and pass a tuple of functions rather than an array. That will allow the compiler to know the exact types of the functions. Unfortunately, the return types do not seem to be inferred in that case: the fact that there is a loop over the functions does not appear to be handled (yet).

---

_[View the full topic](https://discourse.julialang.org/t/type-stability-when-arguments-are-functions/4734)._
