In my setup I'm compiling Lua as part of my project, and when I turn on LTO via CMAKE_INTERPROCEDURAL_OPTIMIZATION, the return listed below is considered unreachable by MSVC. I guess MSVC can analyze through multiple Lua calls and determine that luaL_error eventually calls a function marked noreturn. I'm compiling with /W4 /WX and this becomes an error during linking, so marking the library as SYSTEM in cmake doesn't suppress the error. Commenting out the return fixes the issue in MSVC, but I don't know if it'll break other compilers.
Tested with Sol 3.3.0, Lua 5.4.4, cl 19.36.32532 x64.
Sol config: SOL_USING_CXX_LUA, SOL_ALL_SAFETIES_ON, SOL_CHECK_ARGUMENTS
In my setup I'm compiling Lua as part of my project, and when I turn on LTO via
CMAKE_INTERPROCEDURAL_OPTIMIZATION, the return listed below is considered unreachable by MSVC. I guess MSVC can analyze through multiple Lua calls and determine thatluaL_erroreventually calls a function markednoreturn. I'm compiling with/W4 /WXand this becomes an error during linking, so marking the library asSYSTEMin cmake doesn't suppress the error. Commenting out the return fixes the issue in MSVC, but I don't know if it'll break other compilers.Tested with Sol 3.3.0, Lua 5.4.4, cl 19.36.32532 x64.
Sol config:
SOL_USING_CXX_LUA,SOL_ALL_SAFETIES_ON,SOL_CHECK_ARGUMENTShttps://github.com/ThePhD/sol2/blob/eab1430ccdbf61a0d61d11bf86b4975838dcfb9a/include/sol/stack_core.hpp#L335-L343
I can try to provide a complete test case if necessary.