mirror of
https://github.com/facebook/sapling.git
synced 2024-10-17 04:08:01 +03:00
79a60403f7
Summary: The histpack format requires that entries in each file section be written in topological order, so that future readers can compute ancestors by just linearly scanning. Let's make the rust mutable history pack support this. Technically the rust historypack reader does not require this for now, but the python one does, so we need to enforce it. Reviewed By: kulshrax Differential Revision: D10441286 fbshipit-source-id: dfdb57182909270b760bd79a100873aa3903a2a5 |
||
|---|---|---|
| .. | ||
| argparse | ||
| bookmarkstore | ||
| cdatapack | ||
| clib | ||
| commitcloudsubscriber | ||
| configparser | ||
| encoding | ||
| hg_watchman_client | ||
| hgpython | ||
| indexedlog | ||
| linelog | ||
| lz4-pyframe | ||
| minibench | ||
| mpatch | ||
| mpatch-sys | ||
| pathmatcher | ||
| radixbuf | ||
| revisionstore | ||
| third-party | ||
| treestate | ||
| types | ||
| 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).