On Mon, Oct 1, 2012 at 8:36 PM, Jonathan M Davis
<jmdavisp...@gmx.com> wrote:
[Creating a new thread for this]
__ctfe exists purely so that you can provide an alternate
implementation which
works at compile time when the normal implementation doesn't
(since CTFE _is_
more restrictive in what it allows than running a function at
runtime is).
Something I wanted to ask for a long time: is there any runtime
speed penalty in using __ctfe? I have functions that are OK at
runtime and do not work at compile-time. If I find a way to make
them work at CT and use __ctfe to distinguish the two branches,
will runtime execution become slower?
