# Formalizing Julia in Lean (and finding 400+ bugs in Base)

**URL:** <https://discourse.julialang.org/t/formalizing-julia-in-lean-and-finding-400-bugs-in-base/140243>\
**Category:** General Usage\
**Created:** [October 25, 2026, 7:07pm UTC](https://discourse.julialang.org/t/formalizing-julia-in-lean-and-finding-400-bugs-in-base/140243 "2026-10-25T19:07:11Z")\
**Posts on this page:** 1\
**Showing post:** 32

<div class="post-metadata">

**Author:** ![Tarny\_GG\_Channie](https://avatars.discourse-cdn.com/v4/letter/t/3bc359/32.png) [@Tarny\_GG\_Channie](https://discourse.julialang.org/u/Tarny_GG_Channie)\
**Post date:** [November 6, 2026, 3:01am UTC](https://discourse.julialang.org/t/formalizing-julia-in-lean-and-finding-400-bugs-in-base/140243/32 "2026-11-06T03:01:33Z")

</div>

I mean… programmatically checkable interface designs are often proposed in Julia, but they often end up not working well enough because Julia is reliant on a permissive system. Even errors like “undefined variables” or even “no such thing exists” are only catchable runtime error and not something Julia will refuse to compile. When it does work well enough for one class of problem, it still could break generics (or even things like dual number used in autograd) and so on if the check was too conservative. Lean avoids this issue because anything that can be formally proven can be made correct. A standard static analysis tool doesn’t have that resource.

---

_[View the full topic](https://discourse.julialang.org/t/formalizing-julia-in-lean-and-finding-400-bugs-in-base/140243)._
