fabpot/Twig — comment on commit 1d6dfad4f55c721ec7b6e674ef225b8442bce896
File:  line 0
By nikic:

@stof I don't get that argument. The introduction of `do` would change the semantics of Twig functions towards becoming full featured PHP functions with the option to not return. I understand that currently it doesn't make sense for a function to not return, but it's not like that's carved in stone and must not change. I really can't detect any superiority of `{% flush %}` over `{% do flush() %}`, actually one could even argue that the latter reads nicer.