C++17 constexpr everything, or as much as the compiler can

Re:C++17 constexpr everything, or as much as the compiler can by reikonomusha on Thursday December 28, 2017 @08:46AM (#16021942)

All of this is easy in Common Lisp, which includes interactive compile-time debugging. You can use #., EVAL-WHEN, LOAD-TIME-VALUE, and other things to control evaluation time, and use the same, usual, interactive debugger that you use for runtime code, without any extra infrastructure or scaffolding.

In C++, to debug failed constexpr’s, often, you have to make it a non-constexpr and debug at runtime.

[ Parent | on HN ]

Re:C++17 constexpr everything, or as much as the compiler can by alexeiz on Thursday December 28, 2017 @12:19PM (#16023327)

Is there anything not easy in Common Lisp?

[ Parent | on HN ]

Re:C++17 constexpr everything, or as much as the compiler can by jcelerier on Thursday December 28, 2017 @10:24AM (#16022434)

or you can just use a C++ repl like Cling ?

[ Parent | on HN ]

Re:C++17 constexpr everything, or as much as the compiler can by HelloNurse on Thursday December 28, 2017 @11:00AM (#16022734)

What the C++ repl does with constexpr functions would be unrelated to the code generated by the actual C++ compiler.

[ Parent | on HN ]

Re:C++17 constexpr everything, or as much as the compiler can by marmaduke on Thursday December 28, 2017 @06:53PM (#16026225)

since Cling is just Clang in a REPL, it seems like it would be good idea

[ Parent | on HN ]

Re:C++17 constexpr everything, or as much as the compiler can by reikonomusha on Thursday December 28, 2017 @10:32AM (#16022485)

I’m not sure that’s even close to equivalent in execution-time debugging, and doesn’t work well with large, existing code bases with crafted build steps. These are transparent, non-issues in Common Lisp.

[ Parent | on HN ]