|
|
|
|
|
|
by int_19h
3172 days ago
|
|
|
One thing I'd love to see, in conjunction with this, is some kind of MVCC with snapshot transactions on filesystem level. So you don't really mutate files - you create new versions of them, and then old versions get GC'd eventually if nothing references them (which may not be the case if you e.g. have a backup). Problem is, our existing file I/O APIs are very much centered around the notion of mutable files, and globally shared state with no change isolation. |
|
|