# Core.tuple() warntype

**URL:** <https://discourse.julialang.org/t/core-tuple-warntype/33375>\
**Category:** Performance\
**Created:** [January 15, 2020, 2:15am UTC](https://discourse.julialang.org/t/core-tuple-warntype/33375 "2020-01-15T02:15:16Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [January 17, 2020, 6:50am UTC](https://discourse.julialang.org/t/core-tuple-warntype/33375/21 "2020-01-17T06:50:30Z")

</div>

Just search for dicussions with examples, eg

> [@When should we use \`@nospecialize\`?](https://discourse.julialang.org/t/when-should-we-use-nospecialize/10392):
>
> The manual is sketchy about the use of @nospecialize (maybe it is still WIP?). I gather it is a necessary optimisation to avoid overburdening the dispatch tables. Is the end user advised to use this macro in some specific circumstance or coding pattern?

> [@Very large compilation time (and space)](https://discourse.julialang.org/t/very-large-compilation-time-and-space/28342/):
>
> In a previous post, I mentioned a small interpreter that I wrote both in direct style and in continuation-passing style. In the first case, Julia very quickly compiles the interpreter methods as they are being used. In the second case, however, this process takes inordinate amounts of time even for trivial inputs and, for simple but non-trivial inputs, it does not even finish because it exhausts the memory (32 GB). Given the size of the interpreter, it was not practical to show it here so I tri…

---

_[View the full topic](https://discourse.julialang.org/t/core-tuple-warntype/33375)._