elucent

The current issue is less of an implementation issue, and more of a compatibility one - the GC itself is mostly done, but precise GC hinges on being able to...

Oh, I think there'll end up being a reasonable solution. I just haven't figured it out yet. Perhaps more likely than either of those two options would be some kind...

Added to 1.0 release in the new "releases" project. Work is progressing on this in `compiler/ssa.cpp`! Register allocation has largely been moved to the new Jasmine bytecode instruction set.

Leaving this open since we should still do it at some point, but I've detached it from any particular release.

This deserves deeper discussion and evaluation - how much of a stdlib do we consider necessary for 1.0? Adding this to the 1.0 release column, but it might be reasonable...

I'm kind of morally opposed to `unsafe` as a language feature - if we add a perfectly functional feature that is often the best solution to a problem, why actively...

Though it's become a little more indirect, FFI should definitely be achievable in the 1.0 release. There's a few methods we could employ to achieve this, which probably deserve independent...

Tentatively scheduling this for 1.1 - it's probably not too hard to add, but I don't know that it's essential for the language to function initially.

I'm a bit dubious of any result coming from V...but yes, Basil will remain unboxed by default. These will behave primarily like OCaml's `ref` types - a means of boxing...

Lobster uses a similar approach. Basil's garbage collector is not reference-counting so I'm not sure it's as applicable or useful (RC needs optimization really bad due to poor locality and...