Design Principle: Resilient vs. Strict

[stasm]

A dedicated issue for discussing one of the design dimensions proposed in #50.

Resilient vs. Strict

How far do we want to go to provide fault tolerance in case of runtime errors (an error in a formatter, a missing variable, a mismatched selector, etc.) and syntax errors (unclosed placeable, missing delimiter, invalid comment sigil, etc.)?

Related Issues: #45

[Fleker]

In some cases, having a strict runtime will enforce best practices and allow build systems to catch errors early. I think being more strict will be beneficial for large applications. Still, that can impose a higher burden on small developers. It may be optimal to mark these syntax issues as warnings, with a runtime parameter to "fail on warning" to provide a strict mode.

[zbraniecki]

At Mozilla we enable eager errors in CI, tests and custom builds, and no visible errors plus strong recovery in production

[aphillips]

Closing this issue as stale. Please open new specific issues if needed.