Lexer and parser generators using CTFE

[Andrei Alexandrescu]

On 3/1/12 1:54 AM, Marco Leise wrote:
> Am 29.02.2012, 02:30 Uhr, schrieb Piotr Szturmaj <bncrbme at jadamspam.pl>:
>
>> CTFE code can be much slower than native one, and I would like to see
>> some kind of compiler cache for such code.
>
> I second this. As a fan of clean optimizations this is one of the things
> I tossed around my head for a while. It could use a cache file or the
> compiler could be started as a daemon process keeping a memory cache.
> All code that is called through CTFE would go into the cache, indexed by
> the internal representation of the function body and parameters.

I think this is the kind of development that will be naturally motivated 
and pushed by serious CTFE applications pushing the boundary. I'm not 
very worried about it right now as about investigating CTFE potential 
and blockers.

Andrei