# Why isn't \`size\` always inferred to be an Integer?

**URL:** <https://discourse.julialang.org/t/why-isnt-size-always-inferred-to-be-an-integer/75139>\
**Category:** General Usage\
**Tags:** inference, compilation\
**Created:** [January 24, 2022, 4:09pm UTC](https://discourse.julialang.org/t/why-isnt-size-always-inferred-to-be-an-integer/75139 "2022-01-24T16:09:16Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)\
**Post date:** [January 24, 2022, 6:58pm UTC](https://discourse.julialang.org/t/why-isnt-size-always-inferred-to-be-an-integer/75139/20 "2022-01-24T18:58:08Z")

</div>

~~Type instabilities in end-packages tend to impact _runtime_ speed, not the (pre-)compile time.~~ In upstream libraries, yes, they can indeed become one of the magnets for invalidation, but ~~I don’t think they’re typically troublesome at the point where I think you are.~~

This conversation is now circling back to the original thread from which it was split — we can go back to [Taking TTFX seriously: Can we make common packages faster to load and use](https://discourse.julialang.org/t/taking-ttfx-seriously-can-we-make-common-packages-faster-to-load-and-use/74949/) for concrete tips for reducing that compile time.

---

_[View the full topic](https://discourse.julialang.org/t/why-isnt-size-always-inferred-to-be-an-integer/75139)._