chc4

Is this the Matrix spec proposal that is currently implemented by Element (and Synapse?) for their reactions? Did they actually implement it already without reactions being standardized, or is there...

Huh, ok. I understand the reasoning, but having the reference client and reference server implement non-standardized parts of the Matrix spec is a pretty bad look.

We don't currently handle thread locals in JIT closures anyways, so just compiling on another thread is always fine for now.

I think you could do something neat with having Lineiform return a Pin closure, so that the async jit compilation actually just patches the function pointer in the closure vtable...

I think you'd need Pin, since you'd want to hand out a pointer to the closure's vtable that it should atomically patch when it's done compiling; this means that the...

Once we have this I'd like to do a bunch of cool optimizations like loop invariant code motion and *intelligent* loop unrolling. They're probably really hard to implement without a...

Instead of doing 1 or 2, we do technically have a third option: do an initial "slow" instrumented execution of the function while collecting trace information, and do lazy basic...

This has it's own set of issues - the most important being that I have to do my own register allocation now instead of being able to steal Cranelift's (which...

Started development on the `tangle` branch.

I merged the tangle branch into mainline; it isn't isn't nearly good enough to switch to yet, but it does implement a register allocator (without spilling support) and Technically Works(tm).