Closed yackimoff closed 2 years ago
That is intended... due to some technical limitations using xpcall with its error handler is unsafe/unpredictable for users at runtime which may result in random crashes.
Due to this we essentially replaced xpcall with a pcall that contains additionally the stack trace in its error object it returns... since thats the most common usecase for the error handler...
Until we find a solution for the issue "c-call boundary error", you wont be able to use xpcall
the normal way. Since we now also experience the same issue with string.gsub
and a handler function, the importance of that matter rose, but I cant tell you when and if a workaround for these problems will be created...
Describe the bug
xpcall
should receive error handler as second parameter and vararg parameters after it, which it should pass to a wrapped function. But it passes error handler as the first parameter to the function.