Oscar Spencer
Oscar Spencer
Printers can be registered for exceptions, but these values are only shown when an error is thrown. `Exception.print()` should return the string value of an exception.
Printers for exceptions can be registered via `Exception.registerPrinter`, which are used whenever an exception is thrown. Besides an `Exception.print()`, should the standard `toString` and `print` also use the registered printers?
We previously could not print tuple types properly and we should add a test. See https://github.com/grain-lang/grain/pull/1324
In Grain, when types are not exported they appear abstract to the consuming module. However, we expose _all_ types defined in that module as abstract ones, when it should only...
Example: ```grain for (let mut j = 0; j < 10; j += 1) { let rec foo = () => { print("never executed") foo() } void } ``` `foo`...
See also https://github.com/grain-lang/grain/pull/590 We currently read and parse a file to determine its dependencies, and have to read and parse it again later when compiling. We should be able to...
The addition of these types would allow better type safety and code clarity. The Int32 and Int64 types would become the signed variants. This signedness would also affect printing. Proposed...
Back in the day (before we had proper modules), we had a DOM standard library. This should be rewritten so it is usable again, and with better types.
I realized that in C/Rust you can casually use the `open` system call and things just... work. That seemed surprising to me, since all WASI gives us is `path_open`, similar...