mirror of
https://github.com/facebook/sapling.git
synced 2024-10-08 07:49:11 +03:00
6158355747
Summary: In an upcoming diff we'll start writing the actual history pack data file. The file section headers are part of that file, so let's implement the serialization logic and unit test it. Reviewed By: markbt Differential Revision: D9231400 fbshipit-source-id: eb1494e3b8fe3419f77edcaab25f640b48f16e4b |
||
|---|---|---|
| .. | ||
| 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).