allow safe goroutine usage

[TorchedSammy]

Currently when using golua in multiple goroutines it may cause a panic. I noticed this when I was using an event emitter which emitted events async via gorouties which results in a lot of random errors (and panics) shown here:

• [ISSUE] runtime error: invalid memory address Rosettea/Hilbish#197
• fix: more than 1 handler on event causes errors Rosettea/Hilbish#192

[arnodel]

Sorry for the very late response. Yeah, currently it is not safe to use the same golua.Runtime instance from multiple goroutines. It was not a design constraint, so I think it would be challenging to make it work in the most general case.
Depending on what you need it might be possible to make it work though, for example it could be possible to make a thread safe version of the Table data structure and that might provide enough thread safety (perhaps at a non-insignificant performance cost).

[TorchedSammy]

At the very least, I want to run Lua event handlers asynchronously which I was able to do previously with gopher-lua. I also added a function in Lua that will run a callback in a goroutine.

I liked how gopher-lua added stuff that allowed parallel Lua code in the style of Go, with a channel type, select function, goroutine safety, etc.

[arnodel]

Ok, would you be able to give me an example of API you would like to use?

[TorchedSammy]

What do you mean?

[arnodel]

If you wrote an example of how you would like to write some code that achieves that you want.

[TorchedSammy]

go func() {
	rt.Call1(...)
}()

Being able to call functions and run Lua code in multiple goroutines at the same time.