mirror of
https://github.com/facebook/sapling.git
synced 2024-10-09 00:14:35 +03:00
052d0e3708
Summary: We (me and Aida) wanted to have something that could be used instead of Command decorator that we have in python and we came up with the following trait. Differential Revision: D7754930 fbshipit-source-id: 15f412d07045e7d8b229801ec3094664f78f801b |
||
|---|---|---|
| .. | ||
| argparse | ||
| cdatapack | ||
| clib | ||
| indexedlog | ||
| linelog | ||
| minibench | ||
| pathencoding | ||
| pathmatcher | ||
| radixbuf | ||
| third-party | ||
| treestate | ||
| vlqencoding | ||
| watchman_client | ||
| 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).