How does this compare to Ezno? It evaluates types dependently even, so that something like `const x: 5 = 4 + 2` creates a compile time error, as it knows x equals 6, not 5 like its type states.
ESInfer and Ezno work on different layers, in my opinion. ESInfer provides a general ability to type-check code, yet Ezno improves a type system by adding the dependent type support. Ezno can work on top of typescript and could work with ESInfer, right? An easy way to do this is to use ESInfer to generate typescript annotations and then pass it to Ezno.
See also, Hegel, which also wants to statically type check JS without TS necessarily. Looks like this space is heating up!
Very glad to see so many afford to make javascript a better language there! I played it around, and I found Hegel seems not to support dynamic features like modifications of objects or prototypes. And this is the real difficulty of implementing a sound and complete type system to a dynamic script language like javascript.
Can you share if they have any plans for that?
https://hegel.js.org/try#GYVwdgxgLglg9mABFApgZygCgIYEpEDeAUI...
https://hegel.js.org/try#MYewdgzgLgBCMF4YG8CGAuFAjTBGAvvgNwB...