https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106611
--- Comment #9 from Jiang An <de34 at live dot cn> --- (In reply to Nikolas Klauser from comment #8) > I agree that the wording is a bit ambiguous, but GCC should decide on one > of them instead of returning different results between the type trait > builtins and the noexcept operator. The result of noexcept operator is unambiguously specified in the standard and GCC is already correct. So the suggestion is equivalent to detecting the exception specifications only. I've mailed the LWG Chair to submit an LWG issue that requests clarification of "is known not to throw any exceptions". FYI, there's at least one library implementor holding the same opinion as yours. https://quuxplusone.github.io/blog/2023/04/17/noexcept-false-equals-default/
