# A case for inline type annotations

**URL:** <https://forum.elixirforum.com/t/a-case-for-inline-type-annotations/71220>\
**Category:** Discussions\
**Tags:** static-types, types, static-typing\
**Created:** [June 11, 2025, 1:01am UTC](https://forum.elixirforum.com/t/a-case-for-inline-type-annotations/71220 "2025-06-11T01:01:03Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![plcholder](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/plcholder/32/41212_2.png) [@plcholder](https://forum.elixirforum.com/u/plcholder)\
**Post date:** [June 11, 2025, 10:52am UTC](https://forum.elixirforum.com/t/a-case-for-inline-type-annotations/71220/10 "2025-06-11T10:52:25Z")

</div>

Well said, static types save cost in the long run, they can help set the programmers intentions with the right invariant’s. I love writing elixir, but i always have that weird feeling that I wrote something wrong somewhere, that will comeback to bite me maybe not now, maybe in a few weeks, years etc ofc BEAM idiom of let it crash, does mitigate a bit of the worries but it is still a far cry from something like rust were you can guarantee things hold in most cases & you don’t need to write insane conditionals just to make sure some input is the right type

---

_[View the full topic](https://forum.elixirforum.com/t/a-case-for-inline-type-annotations/71220)._