Excessive noexcept

[GitSparTV]

Hi, I found a function where noexcept breaks catching because an exception can actually occur.

As example: basic_table_iterator& operator++() noexcept shouldn't be noexcept because lua_next in LuaJIT can throw an error.

I assume this isn't the only place where something like this might happen

[Perl99]

LuaJIT is written in C, it does not throw C++ exceptions on its own

[GitSparTV]

@Perl99

LuaJIT is written in C, it does not throw C++ exceptions on its own

It does. You can catch LuaJIT errors with catch (...). It can also rethrow error made during Lua call (see 1, and 2)

The problem with noexcept here that if lua error is thrown, I can't catch it because of this. It goes straight to termination