Dust.js cached partials (in development env)

[me-ascii]

Based on: #33

Have to clean dust.cache = {} each time render.
Please revert the auto-cleaning.

[ForbesLindesay]

I'm not clear, why should the auto-clearing of the cache be removed?

[me-ascii]

If use partials you have to restart the server after each partial-templates update.
Because dust stores compiled partials, even if the { cache: false } flag is set
By default dust keeps all compiled files in dust.cache

[ForbesLindesay]

Ah, I get it, the change was reverted, and you want the behavior that that pull request introduced back?

This got lost by accident in e0cabb1

[ForbesLindesay]

This is a dupe of #76 but that needs re-basing anyway. Once #85 is merged I'll submit a P.R. for dust.

P.S. I'll also make the same change in transformers (my own slightly more feature rich version of consolidate.js) right away.

[doowb]

Closing this since the dust engine cache is cleared now before rendering a file.