mirror of
https://github.com/facebook/sapling.git
synced 2024-10-11 09:17:30 +03:00
668ba5165c
Summary: You can currently iterate over indexlog entries, but there's no way to iterate over the keys without keeping a copy of the index function with you. Let's add a key iterator function. Reviewed By: quark-zju Differential Revision: D13010744 fbshipit-source-id: 1fcaf959ae82417e5cbafae7c1927c3ae8f8e76a |
||
|---|---|---|
| .. | ||
| argparse | ||
| bookmarkstore | ||
| cdatapack | ||
| clib | ||
| commitcloudsubscriber | ||
| configparser | ||
| encoding | ||
| hg_watchman_client | ||
| hgpython | ||
| indexedlog | ||
| linelog | ||
| lz4-pyframe | ||
| minibench | ||
| mononokeapi | ||
| mpatch | ||
| mpatch-sys | ||
| pathmatcher | ||
| radixbuf | ||
| revisionstore | ||
| third-party | ||
| treestate | ||
| types | ||
| 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).