# Julia never stops compiling for new recursive Vector types

**URL:** <https://discourse.julialang.org/t/julia-never-stops-compiling-for-new-recursive-vector-types/110232>\
**Category:** Internals & Design\
**Tags:** performance, recursion, quadratic\
**Created:** [February 15, 2024, 3:25am UTC](https://discourse.julialang.org/t/julia-never-stops-compiling-for-new-recursive-vector-types/110232 "2024-02-15T03:25:50Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![Benny](https://avatars.discourse-cdn.com/v4/letter/b/49beb7/32.png) [@Benny](https://discourse.julialang.org/u/Benny)\
**Post date:** [February 15, 2024, 8:21pm UTC](https://discourse.julialang.org/t/julia-never-stops-compiling-for-new-recursive-vector-types/110232/19 "2024-02-15T20:21:54Z")

</div>

> [@mbauman](#):
>
> generating thousands of distinct types you’re going to hit compilation bottlenecks. That’s just how Julia works.

Really any language that compiles and optimizes methods over specific types. In such cases where arbitrarily many input types are generated, perhaps more than they are reused, there’s `@nospecialize` and `@nospecializeinfer` to opt out.

---

_[View the full topic](https://discourse.julialang.org/t/julia-never-stops-compiling-for-new-recursive-vector-types/110232)._