atomgalaxy/wg21-cust-points

Should validity of noexcept definitions be checked earlier?

Opened this issue · 1 comments

lewissbaker commented

wg21-cust-points/tests/002_noexcept.cpp

Line 5 in cb4c9d1

constexpr auto cpo(auto &&x) default { return 2; }

In cases where the declaration is declared unconditionally noexcept(true) should it be ill-formed to declare a generic default implementation that is unconditionally noexcept(false)?

Should this example at least demonstrate that declaring a non-generic override/default that has mismatching noexcept should be diagnosed as ill-formed at point of declaration?

atomgalaxy commented