mirror of
https://github.com/facebook/sapling.git
synced 2024-10-12 17:58:27 +03:00
25f9843dc0
Summary: Given that the on-the-wire representation of file and tree data is essentially the same, we can reuse our existing structs for file fetching for tree fetching. As such, we should rename these structs to make it clear that they are not just for file data. (This also involves updating some comments/variable names to make sure everything is consistent.) Reviewed By: singhsrb Differential Revision: D15286690 fbshipit-source-id: 8c7fa4392057e90a9f19beb17b0bbcbf04b7e8e7 |
||
|---|---|---|
| .. | ||
| argparse | ||
| asyncrevisionstore/src | ||
| bookmarkstore | ||
| cdatapack | ||
| clib | ||
| commitcloudsubscriber | ||
| configparser | ||
| cpython-ext | ||
| cpython-failure | ||
| dag | ||
| drawdag | ||
| edenapi | ||
| encoding | ||
| hg_watchman_client | ||
| hgpython | ||
| indexedlog | ||
| linelog | ||
| lz4-pyframe | ||
| manifest | ||
| minibench | ||
| mpatch | ||
| mpatch-sys | ||
| mutationstore | ||
| nodemap | ||
| pathmatcher | ||
| radixbuf | ||
| revisionstore | ||
| third-party | ||
| treestate | ||
| types | ||
| url-ext | ||
| 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).