Javier

ah, also note that there are section anchors at the trace boxes, so once you get a dump online, you can copy/paste the url to a specific trace.

funny. the original issue was "lets make it useful for non-github packages" (and maybe someday even usable for non-git too) first answer: "not interested" side comment: "lets add some github-dependent...

well, my feeling is not about the interpreter implementation, but it seems that FFI is anathema to any interpreter.

would have to check the sources to be sure, but i think root traces start when the interpreter hits a hotspot (underflow of the hashed `hotcount` slot); while a side...

i think the negated form (eg, `~4u` for a string) is useful for 32-bit NaN-tagging, because the whole 32 bit word is the tag, so it's mostly 1s, as required...

Note that loom currently has very small runtime overhead in terms of time, but might be perceptible in terms of memory. It's because the hooks installed only record data, all...

yes, that sounds reasonable. i don't think it would mean too much removed code, `lib_jit.c` isn't that long or complex; but i guess every little bit helps. the main goal...

GC finalizer shouldn't be a problem, it's (mostly) the same code as in Lua 5.1; the call to the finalizer is done with the interpreter in a sane state. from...

BTW, both the jit events and profiler run in a preallocated Lua thread (coroutine?), which simplifies the separation of states. of course, the global objects (G, J, anything else?) are...

i like this; but is that super trace supposed to actually contain a copy of (some of) the IR of the parent trace, or is it just an abstract construct...