Golua – A Lua 5.3 engine implemented in Go

Re:Golua – A Lua 5.3 engine implemented in Go by wahern on Friday November 16, 2018 @11:54AM (#18469919)

> The VM is designed differently (I'm encouraging Brian to write a blog post about this), but in a nutshell it is designed for better error handling and for adding a debugger

Looking at the VM, they implement function calls by recursively re-entering the VM in Go. The VM implements neither tail calls nor coroutines, and I don't see how they could implement the latter without some serious refactoring.

Perhaps by adding a debugger they mean they implemented the VM such that they could repurpose existing Go debuggers, which is why there's a 1:1 mapping between the Lua call chain and the Go runtime call chain.

[ Parent | on HN ]

Re:Golua – A Lua 5.3 engine implemented in Go by mfer on Friday November 16, 2018 @12:08PM (#18470010)

This was open sourced very early. It is being built with the intent of supporting Helm v3 and by open sourcing it early it enables other Helm maintainers to get involved and to import it into Helm v3 early.

I expect more docs, details, and improvements will be coming

[ Parent | on HN ]

Re:Golua – A Lua 5.3 engine implemented in Go by wereHamster on Saturday November 17, 2018 @05:27AM (#18474885)

You mean this helm: https://helm.sh?

[ Parent | on HN ]

Re:Golua – A Lua 5.3 engine implemented in Go by stcredzero on Friday November 16, 2018 @02:48PM (#18471449)

in a nutshell it is designed for better error handling and for adding a debugger

Better debugging is one of the big things holding Lua back, IMHO.

[ Parent | on HN ]

Re:Golua – A Lua 5.3 engine implemented in Go by nikki93 on Friday November 16, 2018 @05:54PM (#18472616)

I feel like the main thing to work on here is the frontend, given the "debug." library built into Lua(JIT). ZeroBrane has a frontend, for example.

[ Parent | on HN ]