# New Blog Post: Introducing checked-literals: compile-time bounds checking for numeric literals

**URL:** <https://clash-lang.discourse.group/t/new-blog-post-introducing-checked-literals-compile-time-bounds-checking-for-numeric-literals/112>\
**Category:** Blogs/News\
**Created:** [April 7, 2026, 2:58pm UTC](https://clash-lang.discourse.group/t/new-blog-post-introducing-checked-literals-compile-time-bounds-checking-for-numeric-literals/112 "2026-04-07T14:58:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![cuddlefishie](https://yyz2.discourse-cdn.com/free1/user_avatar/clash-lang.discourse.group/cuddlefishie/32/4_2.png) [@cuddlefishie](https://clash-lang.discourse.group/u/cuddlefishie)\
**Post date:** [April 7, 2026, 2:58pm UTC](https://clash-lang.discourse.group/t/new-blog-post-introducing-checked-literals-compile-time-bounds-checking-for-numeric-literals/112/1 "2026-04-07T14:58:07Z")

</div>

Ever got caught with a numeric literal that was too big for a Clash (or otherwise Haskell) Type and didn’t get a warning or an error?

Yeah, us too! So we introduce a new package: `checked-literals` Read more about it in the new post:

> **[Introducing checked-literals: compile-time bounds checking for numeric literals](https://clash-lang.org/blog/0009-checked-literals/)**
>
> A GHC plugin that turns out-of-range numeric literals into type errors