Ben
Eventually want to support ```ts function myRecusiveLoop(i, x) { if (i
Update: after #102 have added multiple entry points to the checker. However it is not fully wired up to Ezno's CLI with: https://github.com/kaleidawave/ezno/blob/1aa77e2aabb9533fb4fe90fa1ac9aaa24136256b/src/cli.rs#L170-L172 The next part (that you can contribute...
Maybe modules (and maybe functions) could be checked in parallel. Just needs `CheckingData` stuff to be behind a `Mutex` and stuff... Somethings: - Blocks still need to be done in...
Currently there exists [`TypeCheckOptions`](https://docs.rs/ezno-checker/latest/ezno_checker/struct.TypeCheckOptions.html), which offers some very basic configuration that isn't really implemented. Thinking further about configuring the checker for certain things. I think it needs to be more...
Currently there is no difference in the representation of properties that are dependent once OR multiple times. aka `{ [a: number]: "value" }` has under a context properties as `[(PropertyKey::Type(*number...
Given something like ```ts function (cb: Function) { const obj = { a: 2 } cb(obj) console.log(obj.a) } ``` This might fail if the function passed as `cb` deletes `a`...
At the time of writing Ezno supports getters on objects and classes. It does this by treating getters the same as regular functions. Then when 'getting' the property it **evaluates...
Current the functions to doing binary operations don't check the types of either side. First a bit of background: There are two functions for binary operators, they are split between...
Currently all diagnostics (type checking errors, warnings, information items) are buffered into a vector which is output. There could instead be a case where the errors are passed to a...
Function `.bind` should be implemented as a constant function which creates a new `Function` type with the `ThisValue` set to the first argument. Then once that is added `.call` and...