You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This implementation depends on using the debug.getinfo, debug.getlocal, and debug.getupvalue functions to interpret expressions in the right environment. I've seen the big warning about debug in the README, so I'm wondering if this code would cause unsafety if used under rlua, despite not mutating anything through debug.
Thanks!
The text was updated successfully, but these errors were encountered:
Depends on your definition of unsafety, really. If it has no bugs, then it probably won't make correct scripts cause memory unsafety. Even if it has no bugs, it could allow incorrect scripts to cause memory unsafety, but you could almost certainly do that already without enabling debug. Even if #116 was fixed, you could almost certainly still do it.
I need to update the README to make the point about the unsafety of the debug library and the safety of rlua a bit more subtle, since the safety situation around PUC-Lua is IMO pretty bleak.
Hello! Thank you for such a high-quality and comprehensive library.
I'm interested in using hishamhm's implementation of string interpolation in a project with
rlua
.This implementation depends on using the
debug.getinfo
,debug.getlocal
, anddebug.getupvalue
functions to interpret expressions in the right environment. I've seen the big warning aboutdebug
in the README, so I'm wondering if this code would cause unsafety if used underrlua
, despite not mutating anything throughdebug
.Thanks!
The text was updated successfully, but these errors were encountered: