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
It is especially important that callbacks, such as those passed to ERR_print_errors_cb, do not throw exceptions. The compiler can enforce this if the callback has the nothrow attribute. Should we add this attribute to the library in the appropriate places?
The text was updated successfully, but these errors were encountered:
Yes, absolutely. (answering without having looked into the code, just from my experience with callback functions used by C originating binaries). But enforcing nothrow abruptly may break a lot of code that doesn't throw but that isn't nothrow, thus there may be a need for a gentle migration (if there is a gentle way at all).
It is especially important that callbacks, such as those passed to ERR_print_errors_cb, do not throw exceptions. The compiler can enforce this if the callback has the nothrow attribute. Should we add this attribute to the library in the appropriate places?
The text was updated successfully, but these errors were encountered: