include keyword breaks Templar
In EJS 0.8, the new include keyword collides with the include() function that https://github.com/isaacs/templar provides. Also, it looks like it has different semantics and behavior. (Templar's include() returns a string. EJS's loads the template inline. Templar's lets you pass specific data. EJS's uses the same data.)
It would be better, I think, to allow this feature to be disabled (and/or the keyword modified) with a configuration option. Is this a reasonable feature in your opinion? If so, I'll write a patch.
option sounds good to me
Would you prefer it to be on by default or off by default?
probably best to leave it enabled by default to BC