I am using the library with a custom cache path, and I track it in Git (since my app is intended for offline install, I want to have it updated and part of my package).
I notice that every time I run the code to update the file, there are differences. I doubt the original file is updated so frequently (at least daily), so I am assuming it is related to the async IO operations - the order of writes to the target file is not necessarily the same as the read of the source.
I was wondering if there is any way to preserve the line order of the original file without significantly affecting efficiency?
I am using the library with a custom cache path, and I track it in Git (since my app is intended for offline install, I want to have it updated and part of my package).
I notice that every time I run the code to update the file, there are differences. I doubt the original file is updated so frequently (at least daily), so I am assuming it is related to the async IO operations - the order of writes to the target file is not necessarily the same as the read of the source.
I was wondering if there is any way to preserve the line order of the original file without significantly affecting efficiency?