Note that -fno-full-laziness may be needed

[unhammer]

This took way too long to find out – could be useful to others who are not able to guess that it would be needed :)

(Though I'm not sure if it's best to have it in README or at the top of Text.XML.Stream.Parse's haddocks?)

[k0ral]

Please correct me if I am wrong, but after reading the article from FP Complete and this comment, the issue does not seem to be specific to xml-conduit, but to any library that uses conduit (or any streaming library in general).
Therefore, I would rather move the -fno-full-laziness suggestion to conduit's README, rather than repeating it in each and every conduit-based library.
What do you think ?

[unhammer]

Where is it most discoverable in practice for people who run into memory issues? The reason I added a PR to xml-conduit was that I was sure it happens there with trivial examples but not sure it happened elsewhere with such trivial examples; but that last comment does seem to suggest it goes for anything depending on conduit >=1.3.

And then to complicate matters, it seems like people have had issues not just with streaming libraries but full laziness in general …