mustache/spec — comment on commit 8c3547c45f041053400398bae3d65195bd65c64f
File:  line 0
By groue:

File-existence check is not expensive.

As an Objective-C developer (we are all a bit strict), I'd tend to think that a reasonable default would be to raise by default, but to allow users to explicitly ask for the dangerous option (ignoring missing partials, maybe with what you call a secondary channel for "mustache warnings"). I especially want to avoid ignoring exceptional situations (the partial was there, and later, for some reason, maybe in production, it vanishes, and the program doesn't complain).

I also understand pretty well that what I've call above a dangerous option is not that dangerous for a javascript developer, for instance: all his templates and partials are in memory, and since he's a motivated TTD developer, his tests will catch the missing partial even if mustache.js does not complain. He may well even use this 'feature' in his own code, with great benefit.

Actually, I'm sorry, but I have no proposal for a better test. Maybe because the current structure of the YAML tests can't express what we are talking about.