# For T in (Float64,) vs let T=Float64

**URL:** <https://discourse.julialang.org/t/for-t-in-float64-vs-let-t-float64/77842>\
**Category:** General Usage\
**Tags:** question\
**Created:** [March 14, 2022, 2:06am UTC](https://discourse.julialang.org/t/for-t-in-float64-vs-let-t-float64/77842 "2022-03-14T02:06:02Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![DNF](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dnf/32/10191_2.png) [@DNF](https://discourse.julialang.org/u/DNF)\
**Post date:** [March 14, 2022, 5:50am UTC](https://discourse.julialang.org/t/for-t-in-float64-vs-let-t-float64/77842/3 "2022-03-14T05:50:14Z")

</div>

This seems similar to the question that came up in this thread: [Can a function return another function?](https://discourse.julialang.org/t/can-a-function-return-another-function/77806)

Apparently, it’s considered a bug or unwanted limitation. But I don’t really see why this _should_ work. Dynamically creating named functions at runtime seems unnatural to me.

Isn’t this metaprogramming, that should require a macro? Or, if you don’t really need a globally defined name, make an anonymous function.

---

_[View the full topic](https://discourse.julialang.org/t/for-t-in-float64-vs-let-t-float64/77842)._