Ruby Lazuli

Coroutines, semicoroutines, `async`/`await`, and more!

2

Unlike [the issue on effects](https://github.com/PatchMixolydic/laria/issues/16), which is mostly just hypothetical "oh this seems like something I might want someday", some form of coroutines would be useful to me today: [Devil's...

Investigate effects/context system?

5

Not sure if it'd have any application for my current use case (game scripting language), but this might be cool for using Laria as a general purpose language. I've run...

How in the world will types be represented in bytecode/Rust?

1

Suppose we have some Laria types: ```rust // This is an opaque native type extern type Entity; enum Option[T] { Some(T), None, } struct Foo[T] { maybe_tup: Option[(T, T)], arr:...

Consider the following code: ```rust extern fn foo() -> i64; extern fn bar() -> !; extern fn wait(seconds: f32); fn main() { wait(5.0); foo(); } ``` If `wait` is registered,...

Lexer tests should check that their output is as expected

1

Several lexer tests currently just emit a diagnostic and hope that you'll think to use `--show-output`: https://github.com/PatchMixolydic/laria/blob/13718184cacd584b32b7532749c46c1e8226c735/laria_compiler/src/script/parser/tests.rs#L33-L53 These tests should check their output themselves.

Better testing

1

UI tests, compile fail tests, and especially integration tests are needed. Currently, the only integration tests are the Laria frontend and Triplicata, neither of which are automated test suites. This...

Add alternative diagnostics output formats

1

Alternative diagnostics output formats may be helpful for different scenarios: * [ ] No span highlighting (may improve screen reader experience? not sure) * [ ] Some form of structured...