> A well designed API won't give you an OOM it'll throw a 'this file is too big' this is possible solution, still it doesn't allow to iterate lines one by one

> A well designed API won't give you an OOM it'll throw a 'this file is too big' this is possible solution, still it doesn't allow to iterate lines one by one and handle large files > Throws path not found. Throws file not found. I think it is some very niche use cases when you need to distinguish between these cases. From another hand there are many places in the code which operate absolute file paths already, and you force them to split path, which is cumbersome. At least two alternative APIs probably are justified to have. > Fastest was suck each one into memory and call split. I really don't think pre-splitting is any kind of performance bottleneck, it is likely 1% of performance compared to all IO stack and subsequent string/objects memory management.