Xavier Deguillard 934b64397b convert to bytes 0.5 ... Summary: The bytes 0.5 is a depencency of newer tokio, it's also newer, and thus better. Staying on 0.4 means that copies between Bytes 0.4 and 0.5 need to be done, this will be especially bad in the LFS code since 10+MB buffer will have to be copied... One main API change is for the configparser. The code used to take Into<Bytes> for the keys, I switched it to AsRef<[u8]>. For hg_memcache_client, an extra copy is performed to build a Delta, since this code uses an old tokio, and is being replaced right now, the effort of switching to a new tokio and new bytes was not deemed worth it, the copy will do for now. Reviewed By: dtolnay Differential Revision: D20043137 fbshipit-source-id: 395bfc3749a3b1bdfea652262019ac6a086e61e0		2020-02-24 10:28:46 -08:00
..
c_api	eden: periodically refresh content store to give it chances to release mapped files	2020-01-17 15:00:01 -08:00
src	revisionstore: move Arc outside of the stores	2020-02-20 14:28:52 -08:00
test	Merge fb-mercurial sources into the eden repository	2019-11-13 20:20:32 -08:00
tools	Move fb-mercurial sources into an eden/scm subdirectory.	2019-11-13 16:04:48 -08:00
Cargo.toml	convert to bytes 0.5	2020-02-24 10:28:46 -08:00
cbindgen.toml	backingstore: add Tree and TreeEntry Rust structs to pass manifest	2019-11-19 18:01:23 -08:00
CMakeLists.txt	Merge fb-mercurial sources into the eden repository	2019-11-13 20:20:32 -08:00