And if so, wouldn't it make sense to have a lazy counterpart of that function?
I've done quick profiling with about 4MB of XML, and it seems on my machine accessing a single element in that file through parseXMLDoc has the same space and time characteristics as accessing all of them: ~4 seconds and ~700MBs of memory on my machine.
Version: xml 1.3.14
Alternatively, if you don't want to include a lazy version, could you perhaps point me in the direction of a an XML parser library that has a similarly simple API and uses Data.Text.Lazy?
And if so, wouldn't it make sense to have a lazy counterpart of that function?
I've done quick profiling with about 4MB of XML, and it seems on my machine accessing a single element in that file through
parseXMLDochas the same space and time characteristics as accessing all of them: ~4 seconds and ~700MBs of memory on my machine.Version: xml 1.3.14
Alternatively, if you don't want to include a lazy version, could you perhaps point me in the direction of a an XML parser library that has a similarly simple API and uses Data.Text.Lazy?