mirror of
https://github.com/facebook/sapling.git
synced 2024-10-11 09:17:30 +03:00
2ea8028d14
Summary: If all of the nodes in a datapack file start with the same byte value, the cdatapack code computed the fanout table incorrectly. If this byte value was anything other than 0x00 it would only be able to find the last node in the pack, and would not be able to find any other nodes. This fixes the code to compute the fanout table correctly in this case. Reviewed By: quark-zju Differential Revision: D8131020 fbshipit-source-id: 84e49befc5776cff96831f6120194466d9c80b35 |
||
|---|---|---|
| .. | ||
| 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).