mirror of
https://github.com/facebook/sapling.git
synced 2024-10-12 17:58:27 +03:00
991a9343b9
Summary: Partially implement open, append, flush, lookup APIs. This shows how things work in general, like how locking works. What's in-memory and what's on-disk etc. Reviewed By: DurhamG Differential Revision: D8156514 fbshipit-source-id: 2de23dcde2f63895f3f3e4f67057aa9520fdfa34 |
||
|---|---|---|
| .. | ||
| argparse | ||
| cdatapack | ||
| clib | ||
| commitcloudsubscriber | ||
| hg_watchman_client | ||
| indexedlog | ||
| linelog | ||
| lz4-pyframe | ||
| minibench | ||
| mpatch | ||
| mpatch-sys | ||
| pathencoding | ||
| pathmatcher | ||
| radixbuf | ||
| revisionstore | ||
| third-party | ||
| treestate | ||
| vlqencoding | ||
| watchman_client | ||
| zstdelta | ||
| 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).