Compile time function execution is the ability of a compiler, that would normally compile a function to machine code and execute it at run time, to execute the function at compile time. This is possible if the arguments to the function are known at compile time, and the function does not make any reference to or attempt to modify any global state (is a pure function).
Even if the value of only some of the arguments are known, the compiler may still be able to perform some level of compile time function execution (partial evaluation), possibly producing more optimized code than if no arguments were known (currently there are no plans to implement such partial evaluation in any D compiler).
Example
In C++, template metaprogramming is often used to compute values at compile time, such as:
template <int N> struct Factorial {
enum {
value = N * Factorial<N - 1>::value
};
};
template <> struct Factorial<0> {
enum { value = 1 };
};
// Factorial<4>::value == 24
// Factorial<0>::value == 1
void foo() {
int x = Factorial<0>::value; // == 0
int y = Factorial<4>::value; // == 24
}
D templates can be used for the same purpose:
template Factorial(int N) {
static if (N == 0)
const int Factorial = 1;
else
const int Factorial = N * Factorial!(N - 1);
}
const int y = Factorial!(0); // == 1
const int x = Factorial!(4); // == 24
But with compile time function evaluation the code used to compute the factorial would be exactly the same as what one would write for run time evaluation (this example code is in the D programming language[1]):
int factorial(int n) {
if (n == 0)
return 1;
return n * factorial(n - 1);
}
// computed at compile time
const int y = factorial(0); // == 1
const int x = factorial(4); // == 24
The use of const tells the compiler that the initializer for the variables must be computed at compile time[2].