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
For functions with the noexcept specifier, we need to find and fix the cases where an exception can potentially reach the outer scope without a proper catch. Such cases break the promise of noexcept and will cause std::terminate() to be called when an exception does happen.
is marked noexcept, but the put method is potentially throwing.
Improve documentation
For all potentially throwing functions (those without the noexcept or noexcept(true) specifier), we need to document (by adding the Doxygen section @throw/@throws/@exception) the exceptions that may be directly thrown from them (i.e. as a result of the throw expression instead of the calls to other potentially throwing functions).
The text was updated successfully, but these errors were encountered:
Improve source
For functions with the
noexcept
specifier, we need to find and fix the cases where an exception can potentially reach the outer scope without a proper catch. Such cases break the promise ofnoexcept
and will causestd::terminate()
to be called when an exception does happen.For instance, currently:
kvikio/cpp/src/bounce_buffer.cpp
Line 32 in 716a99f
is marked
noexcept
, but theput
method is potentially throwing.Improve documentation
For all potentially throwing functions (those without the
noexcept
ornoexcept(true)
specifier), we need to document (by adding the Doxygen section@throw/@throws/@exception
) the exceptions that may be directly thrown from them (i.e. as a result of thethrow
expression instead of the calls to other potentially throwing functions).The text was updated successfully, but these errors were encountered: