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 nurettin on Thursday December 28, 2017 @07:43AM (#16021712)
You could use something like #ifdef NDEBUG #define MY_CONSTEXPR #else #define MY_CONSTEXPR constexpr so when you are running the debug build, everything is debuggable.
[ Parent | on HN ]
Re:C++17 constexpr everything, or as much as the compiler can by skrebbel on Thursday December 28, 2017 @08:51AM (#16021957)
That makes the compiler not complain when your constexpr isn't a valid constexpr.
[ Parent | on HN ]
Re:C++17 constexpr everything, or as much as the compiler can by nurettin on Thursday December 28, 2017 @10:29AM (#16022470)
Until you make release
[ Parent | on HN ]
Re:C++17 constexpr everything, or as much as the compiler can by mike_hock on Thursday December 28, 2017 @10:35AM (#16022510)
After 3 months of development all I have to do is make release and ...
[ Parent | on HN ]
Re:C++17 constexpr everything, or as much as the compiler can by ryandrake on Thursday December 28, 2017 @11:23AM (#16022939)
If you guys are going three days without testing a release build (let alone three months), then you probably have bigger issues to work through than what constexpr is doing...
[ Parent | on HN ]
Re:C++17 constexpr everything, or as much as the compiler can by geezerjay on Thursday December 28, 2017 @01:46PM (#16023939)
The hypothetical odds of having bigger issues does not justify creating additional issues for no reason at all.
[ Parent | on HN ]
Re:C++17 constexpr everything, or as much as the compiler can by nurettin on Friday December 29, 2017 @02:05PM (#16031227)
which is why they should build release more often.
[ Parent | on HN ]