# Llvm\_unreachable is widely misused

**URL:** <https://discourse.llvm.org/t/llvm-unreachable-is-widely-misused/60587>\
**Category:** LLVM Project\
**Created:** [March 1, 2022, 3:57am UTC](https://discourse.llvm.org/t/llvm-unreachable-is-widely-misused/60587 "2022-03-01T03:57:33Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![bjacob](https://sea1.discourse-cdn.com/flex021/user_avatar/discourse.llvm.org/bjacob/32/1043_2.png) [@bjacob](https://discourse.llvm.org/u/bjacob)\
**Post date:** [March 1, 2022, 3:27pm UTC](https://discourse.llvm.org/t/llvm-unreachable-is-widely-misused/60587/8 "2022-03-01T15:27:02Z")

</div>

My point is, APIs _will_ be used incorrectly, code _will_ have bugs, etc. This will always have negative consequences, but using `__builtin_unreachable` makes the consequences worse. I understand that this is a non-issue in an ideal world where we can say that people should write correct code and too bad for them if they don’t, but I don’t live in that world.

---

_[View the full topic](https://discourse.llvm.org/t/llvm-unreachable-is-widely-misused/60587)._
