salman-ca

Regarding #2, the use case is as follows. If you allow the end user to create their own templates, they might write very inefficient templates such as abuse of looping...

Not sure if it is related to #300 but I know the liquid ruby also has an option where it will render the template and ignore any errors it encounters...

I understand what you are saying and I agree with you after thinking about it. Thanks.