On Tuesday, 9 June 2015 at 16:01:34 UTC, Andrei Alexandrescu wrote:
Same as with @safe @nogc @nothrow @pure.

No, these are attributes that change the function's type; constexpr does not.

AIU, it still does something along those lines.

If you don't have ctfeability
expressed in function's contract, you have no idea how you can modify the function's implementation so that to not break other people's code.
Sorry for making c++ look cute again :)

I guess you could do a lot worse than using a unittest to make sure a function is CTFEable.

Isn't it "Speculatively mark everything in sight as ctfe"?

Reply via email to