News for hackers. Stuff that matters.

A comment on C++17 constexpr everything, or as much as the compiler can. Parent comment

Re:C++17 constexpr everything, or as much as the compiler can by mehrdadn on Thursday December 28, 2017 @04:57PM (#16025253)
> But I think you nailed it -- the compiler doesn't have to signal optimization "failures" back to the developer, but it has to for the constexpr case.

Is this true? Where do you see Clang emit a diagnostic in the example in the given article? (https://godbolt.org/g/HKcPFT)

[ Parent | on HN ]
Re:C++17 constexpr everything, or as much as the compiler can by minipci1321 on Thursday December 28, 2017 @05:58PM (#16025824)
You seem to be right -- at least "no diagnostics required" is mentioned a few times in $10.1.5 of N4700. To be honest, my comment is not from the article in the example, but from my own experience, and that is mostly with GCC 7.2.
[ Parent | on HN ]