Michael Eischer c206a101a3 archiver: unify FutureTree/File into futureNode ... There is no real difference between the FutureTree and FutureFile structs. However, differentiating both increases the size of the FutureNode struct. The FutureNode struct is now only 16 bytes large on 64bit platforms. That way is has a very low overhead if the corresponding file/directory was not processed yet. There is a special case for nodes that were reused from the parent snapshot, as a go channel seems to have 96 bytes overhead which would result in a memory usage regression.		2022-07-23 14:45:07 +02:00
..
archiver.go	archiver: unify FutureTree/File into futureNode	2022-07-23 14:45:07 +02:00
archiver_test.go	archiver: unify FutureTree/File into futureNode	2022-07-23 14:45:07 +02:00
archiver_unix_test.go
archiver_windows_test.go
blob_saver.go	archiver: cleanup Saver interface	2022-07-23 14:16:23 +02:00
blob_saver_test.go	Return real size from SaveBlob	2022-07-02 18:55:12 +02:00
buffer.go	archiver: Remove cleanup goroutine from BufferPool	2022-05-29 17:09:16 +02:00
doc.go
file_saver.go	archiver: unify FutureTree/File into futureNode	2022-07-23 14:45:07 +02:00
file_saver_test.go	archiver: unify FutureTree/File into futureNode	2022-07-23 14:45:07 +02:00
scanner.go	archiver: remove unused fileInfo from progress callback	2022-07-23 14:16:23 +02:00
scanner_test.go	archiver: remove unused fileInfo from progress callback	2022-07-23 14:16:23 +02:00
testing.go	Merge pull request #3830 from MichaelEischer/cleanup-repo	2022-07-23 10:46:13 +02:00
testing_test.go
tree.go
tree_saver.go	archiver: unify FutureTree/File into futureNode	2022-07-23 14:45:07 +02:00
tree_saver_test.go	archiver: unify FutureTree/File into futureNode	2022-07-23 14:45:07 +02:00
tree_test.go