In summary, it was dismissed on the basis of "most people don't need this". I would like to contest this. There are a lot of things "most people don't need" but what if the reason for the need is an important edge case (i.e. applications processing large data sets). Surely there are some people processing applications that operate over large data sets?
The text was updated successfully, but these errors were encountered:
I'm not sure what you are asking for. Issue #25160 ended by suggesting opening a proposal for the change. Do you want to do that? Indicate exactly what you think should be added to the text/template API. Thanks.
At a high level, it would be good to not have to (for example) load a 10mb array into memory so that a template can range over it to build a html or text document (that may also end up being 10mb). It would be desirable if a template could range over a Reader object that returns elements one by one.
I am not so interested in prescribing a particular implementation, just trying to work out how to handle requests that trigger high memory usage in my app server.