mirror of
https://github.com/facebook/sapling.git
synced 2024-10-12 09:48:05 +03:00
d543e91b45
Summary: The order of imports we're trying to follow is: std, remote crates (ie: crates.io), local crates (ie: fbcode crates), and crate local. A new line in between each group can be used to prevent rustfmt from re-ordering them. Reviewed By: singhsrb Differential Revision: D14243163 fbshipit-source-id: fbbb07693af14b13ae6b3f4e788972d99193fd64 |
||
|---|---|---|
| .. | ||
| argparse | ||
| asyncpacks/src | ||
| bookmarkstore | ||
| cdatapack | ||
| clib | ||
| commitcloudsubscriber | ||
| configparser | ||
| cpython-ext | ||
| cpython-failure | ||
| 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).