forcing compile time function execution

[Vladimir Panteleev]

On Tuesday, 27 December 2011 at 19:46:31 UTC, Joshua Reusch wrote:
> Am 27.12.2011 20:35, Vladimir Panteleev wrote:
>> Halting problem?
>
> Makes an not-stopping pure function really sense?

No, but you don't know if the user is expecting the function to 
take a long time to run, or it's stuck due to a bug.

> If you evaluate a function creating an infinite loop at 
> compile-time, you get for sure in this state. Then, the 
> compiler could stop the evaluation after some time and print an 
> error/warning or creates runtime code.

The problem is with "after some time". It's not possible to know 
when the compiler should stop. For all it knows, the user is 
doing some compile-time raytracing.