# Why \`Any\` in \`Any\[func1, func2, func3, func4\]\`?

**URL:** https://discourse.julialang.org/t/why-any-in-any-func1-func2-func3-func4/22469
**Category:** New to Julia
**Created:** [March 28, 2019, 4:45pm UTC](https://discourse.julialang.org/t/why-any-in-any-func1-func2-func3-func4/22469 "2019-03-28T16:45:10Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Kiuhnm\_Mnhuik](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kiuhnm_mnhuik/32/7572_2.png) [@Kiuhnm\_Mnhuik](https://discourse.julialang.org/u/Kiuhnm_Mnhuik)
#### Post date: [March 28, 2019, 4:45pm UTC](https://discourse.julialang.org/t/why-any-in-any-func1-func2-func3-func4/22469/1 "2019-03-28T16:45:10Z")

</div>

I’m reading the [_“Performance Tips”_ section](https://docs.julialang.org/en/v1/manual/performance-tips/#Access-arrays-in-memory-order,-along-columns-1) of the official documentation. At the bottom of that section there’s a piece of code that baffles me a little:

```julia
julia> x = randn(10000);

julia> fmt(f) = println(rpad(string(f)*": ", 14, ' '), @elapsed f(x))

julia> map(fmt, Any[copy_cols, copy_rows, copy_col_row, copy_row_col]);
copy_cols: 0.331706323
copy_rows: 1.799009911
copy_col_row: 0.415630047
copy_row_col: 1.721531501

```

Is there any reason behind that `Any`?

---

<div class="post-metadata">

### Author: ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)
#### Post date: [March 28, 2019, 4:51pm UTC](https://discourse.julialang.org/t/why-any-in-any-func1-func2-func3-func4/22469/2 "2019-03-28T16:51:54Z")

</div>

`Any[]` used to be written as `{}`. This was changed in [update manual for tuple type change · JuliaLang/julia@f96e33b · GitHub](https://github.com/JuliaLang/julia/commit/f96e33b1fded4d9671b7ca5fa71e236785257ca6) (4 years ago) and the codebase was probably regex search and replaced. You are right that it is not needed now. Feel free to open a PR to remove it.