mirror of
https://github.com/facebook/sapling.git
synced 2024-10-12 09:48:05 +03:00
e697e7d994
Summary: In order to send batch responses from the API server for data fetching operations, we need to define the types sent over the wire from within `/scm/hg/lib` so that we can deserialize them from within Mercurial. For ease of use, these types implement `IntoIterator` to allow easily iterating over the content (performing type conversions where needed). Reviewed By: quark-zju Differential Revision: D14517259 fbshipit-source-id: 5ee867d8386e6b99cb5b4ed96338aeb7eb6a3e44 |
||
|---|---|---|
| .. | ||
| 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).