CohenArthur
CohenArthur
Keeping first class typing to compile-time fixes the issue. Is that acceptable?
Hi @KyawD9! Welcom to the jinko project :) Are you interested in working on this?
What remains is to add an actual script to benchmark: One that could be parser intensive, one that would be typechecker intensive and one that would be execution intensive (+...
This is probably tied to #476. The type `V` should just produce an error as it hasn't been declared yet
The idea ultimately is to have a `build.jk` script which is ran when downloading different libraries and which relies on a jinko `Package` library, which could contain the following code...
We can now compile for WASM thanks to #430, but we should think about splitting the project more in various ways in order to allow more compilation targets, such as...
I think this might not be necessary for now, and I can't find a way of doing this without using reflection at runtime. What we could maybe do is to...
We can do this by utilizing duck typing once we have proper type inference. By desugaring format strings to the following construct: ```rust "this should expand to a number: {15}...
So we have to consider a few things here, for example instanciation. How do we instanciate a vector with any number of elements without entirely changing the language? Should we...
The Vector type could be responsible for the low level plumbing and allocate memory itself. We could have the following allocating API: ```rust type pointer; // builtin // or type...