mmap thoughts #20
Labels
hard
Things that are hard to implement properly, and might need considerable refactoring
Open ended
Issues that need lots of thinking and trying out different options before coming to a conclusion.
If it's possible to safely write back cowed regions: The changed regions must be written back exactly to avoid undefined behavior. So damage ranges should never cover more than they changed. No merging of damaged ranges with unchanged data inbetween. It should however be possible to merge ranges that are exactly next to each other, like when editing bytes one after another.
If it turns out it's necessary to copy changes to memory buffers separate from cow before saving, keep track of memory that would be needed, and warn user if memory needed would be too great to safely save.
The text was updated successfully, but these errors were encountered: