mirror of
https://github.com/facebook/sapling.git
synced 2024-10-11 09:17:30 +03:00
c18a1d04f1
Summary: We need the ability to iterate over a datastore so we can implement repack and cleanup. In a later diff we'll use this trait to implement repack functionality in a way that it can apply to any store that implements IterableStore. Reviewed By: quark-zju Differential Revision: D8885094 fbshipit-source-id: 0a2b1ab8cf524392d890302c33e386f1cd218d24 |
||
|---|---|---|
| .. | ||
| argparse | ||
| cdatapack | ||
| clib | ||
| commitcloudsubscriber | ||
| configparser | ||
| hg_watchman_client | ||
| indexedlog | ||
| linelog | ||
| lz4-pyframe | ||
| minibench | ||
| mpatch | ||
| mpatch-sys | ||
| pathencoding | ||
| pathmatcher | ||
| radixbuf | ||
| revisionstore | ||
| third-party | ||
| treestate | ||
| vlqencoding | ||
| watchman_client | ||
| zstdelta | ||
| Cargo.toml | ||
| README.md | ||
lib
Any native code (C/C++/Rust) that Mercurial (either core or extensions)
depends on should go here. Python code, or native code that depends on
Python code (e.g. #include <Python.h> or use cpython) is disallowed.
As we start to convert more of Mercurial into Rust, and write new paths entrirely in native code, we'll want to limit our dependency on Python, which is why this barrier exists.
See also hgext/extlib/README.md, mercurial/cext/README.mb.
How do I choose between lib and extlib (and cext)?
If your code is native and doesn't depend on Python (awesome!), it goes here.
Otherwise, put it in hgext/extlib (if it's only used by extensions) or
mercurial/cext (if it's used by extensions or core).