Cacheless Blade templates

[tillkruss]

Currently Blade templates require a path on the local filesystem for caching. See: laravel/framework#14291

It would great if Blade templates could be compiled in-memory from any string, without ever touching the filesystem. Furthermore it would be nice if a driver/store for Blade template could be configured, similar to the session.driver configuration. That way Blade caches could live in Redis, APC, Memcache, a SQL database, the local file system or just in-memory.

["file", "array", "redis", "apc", "memcached", "database"]

I'd be happy to provide a PR.

[franzliedke]

I don't think that's a great idea. Blade templates are not only cached, they are written to a file to be executable. The alternative would be eval and, I suppose, horrible performance.

[garygreen]

Doesn't opcode cache put the files in memory anyway?