Parsing a UTF-16LE file line by line, BUG?

[Nestor via Digitalmars-d-learn]

On Sunday, 15 January 2017 at 16:29:23 UTC, Daniel Kozák wrote:
> This is because byLine does return range, so until you do 
> something with that it does not cause any harm :)

I see. So correcting my original doubt:

How could I parse an UTF16LE file line by line (producing a 
proper string in each iteration) without loading the entire file 
into memory?