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.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Julia messes up integer exponents? | 106 | 8726 | February 21, 2019 | |
| Why I love Julia | 34 | 5481 | October 11, 2019 | |
| Discussion about integer overflow | 188 | 11917 | October 15, 2021 | |
| Did Julia community do something to improve its correctness? | 216 | 16707 | November 4, 2023 | |
| Tonight I hated julia, REPL and overflows | 64 | 7384 | March 14, 2020 |