Josh Goebel

@nesbox Do you have any thoughts/preferences on how we might actually patch the vendored software instead of purely vendoring pristine copies? Are we ok with small _targeted_ patches to achieve...

``` % git diff --stat 3.0.1 lstate.h | 3 +++ lvm.c | 14 +++++++++++++- 2 files changed, 16 insertions(+), 1 deletion(-) ``` 17 line patch against Lua. Works great. My...

> I profiled with the Visual Studio Community 2019. I can try the patch when I'm at the computer again. Well, it's not as simple as I thought, but you...

https://gist.github.com/joshgoebel/7ad81dbd41e858f6daeb805ddabfee4c

No time, sorry. But the patch should be easy enough to apply.

I like that most of our Lua functions have required arguments but in this case I could see making an exception and either: - no output (but confusing if you...

> it is sometimes possible to accidentally call trace with no arguments. This is what persuaded me we should fix this. Lua is weird. :)

> . Maybe trace() should print 'no value' if it's passed something which isn't nil or any other valid value It's possible to detect no arguments - which is what...

> It's been a very long time indeed since I did any C programming We're talking about the Lua runtime here (calling into C), when I say detect arguments you...

You mean as a language you could use to write cartridges? That would be cool, but... > tcc generates x86 code. Do you have some idea how this would work?...