On 6/9/2015 4:25 AM, "Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?=
<[email protected]>" wrote:
When constexpr is part of the prototype you know that it isn't supposed to do
substantial work.
That doesn't follow.
Without it, you risk the compiler spending a lot of time computing
constants/tables that should be done at runtime to save compile time and object
code size. And since C++ programmers expect that level of control, it would have
ended up as a pragma if it was not part of the language?
This is just made up problems.
