Lua 5.3 debug.traceback about lua-compat-5.3

[siffiejoe]

Hi!
Ok, here are the reasons why nothing has happened yet:

We already have an implementation of debug.traceback in compat53/init.lua. This version incorporates the stack trace of the internal coroutine used by our yieldable (x)pcall implementations. As far as I can tell it also does something when the message is nil.

If we add a new implementation of debug.traceback to compat53/module.lua, we should probably adjust the current version in compat53/init.lua as well to make them compatible. Since I haven't figured out a way to share common code between those two files (but I have been wrong on this before), this would involve a lot of extra code and work to fix basically a very rare and minor issue: the nil as message problem. The differences in the stack traces don't really count IMHO, because all our replacement functions cause stack traces (and sometimes error messages) to be different from a genuine Lua 5.3 session (although the current debug.traceback implementation goes to great lengths (unnecessarily so, IMHO) to reformat stack traces).

So I'm currently inclined to revisit this issue later when the stack level problem in current Lua 5.3 has been fixed by the Lua authors.

Suggestions/opinions?

[daurnimator]

Yeah Roberto said that he'd actually fix 5.3's tracebacks in a point release; so the tracebacks themselves can probably be safely ignored.
So it can just be an issue of making debug.traceback nil safe.