Sean Lang

It's pretty simple, you hash the options & input string, that becomes the key in an object, and then the value for that key is the result of compiling the...

Actually, I was totally wrong about needing a hash - JS has [no limit for keysize](http://stackoverflow.com/questions/13367391/is-there-a-limit-on-length-of-the-key-string-in-js-object) so long as it fits in memory, because the key is just a pointer...

I don't think so - it could be in a separate lib if you want, but caching is a pretty basic feature that should be beneficial like 99% of the...

yep - the interface advantage is that an object can only be used in a single process, during the lifetime of that process. leveldb could be caching compiled files for...

I can do one better: I'll show you! :D this is a few lines of the `jobLog`: ``` json [ { "filename": "/usrdata/web/accord/test/fixtures/haml/precompile.haml", "engineName": "hamljs", "method": "compileFile", "duration": 0.000350218, "deps":...

The deps would be in the job log (under the `deps` property), because (usually) we don't know the deps until after the compilation is done. However, proper "tracking" for deps...

Haha, I did chat with you about it - take a look through the readme (which I published just now) & you should remember

It was a part of the conversation on July 18th before we went to "The Bridges" restaurant to celebrate Henry's internship, and was the solution for 1:many compile relations &...

In order to do this, I feel like the compile/render functions (in the adapters, not the base adapter) would need to return a promise for an object, rather than a...

Nope - the dependencies are detected during the compilation. No compilers support getting deps through a separate method. However, I ended up putting the deps in the `jobLog`, so we...