Triton modernization

[kevzhao2]

Checklist for Triton modernization (v2.0.0):

• [ ] Use GitHub actions for testing/generating artifacts/etc
• [ ] Drop .NET Framework 3.5/4.0 support (only supporting .NET standard 2.0/2.1)
• [ ] Support Lua 5.4
• [ ] Look into Lua support of new C# features (such as ref returns, etc.)
• [ ] Improve Lua syntax of indexed properties

More to come as I think of them.

[kevzhao2]

One potential strategy for supporting CLR <-> Lua interop is to make use of dynamic code generation.

For any type T which needs to CLR <-> Lua interop, we can do something like the following:

• [ ] Generate a type-specific metatable that all instances of T will use in Lua, with the following:

  • [ ] __index: A dynamic method which will take the supplied index, and do one of the following: perform a field get, perform a property get, or return a proxy C function for method calling.

  Note that we don't necessarily need to marshal the supplied index to a string if we're just performing direct byte comparisons. This will potentially save a string allocation.

  • [ ] __newindex: A dynamic method which will take the supplied index, and do one of the following: perform a field set or perform a property set.