# Any plan for static type checker?

**URL:** <https://racket.discourse.group/t/any-plan-for-static-type-checker/3669>\
**Category:** General\
**Tags:** rhombus\
**Created:** [April 1, 2025, 2:02pm UTC](https://racket.discourse.group/t/any-plan-for-static-type-checker/3669 "2025-04-01T14:02:33Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![mflatt](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/mflatt/32/6_2.png) [@mflatt](https://racket.discourse.group/u/mflatt)\
**Post date:** [April 1, 2025, 3:21pm UTC](https://racket.discourse.group/t/any-plan-for-static-type-checker/3669/4 "2025-04-01T15:21:12Z")

</div>

I would not say that Shplait is on the direct path to a Typed Rhombus. It's an experiment that could inform a future Typed Rhombus in the way that type constraints are gathered for a finishing unification pass. Otherwise, though, it's a domain-specific language that's intentionally limited.

Typed Rhombus is definitely of interest, but I don't know of a specific plan to get there, as yet.

---

_[View the full topic](https://racket.discourse.group/t/any-plan-for-static-type-checker/3669)._