mirror of
https://github.com/facebook/sapling.git
synced 2024-10-10 08:47:12 +03:00
6ae1cf9619
Summary: The rust pack stores currently have logic to refresh their list of packs if there's a key miss and if it's been a while since we last loaded the list of packs. In some cases we want to manually trigger this refresh, like if we're in the middle of a histedit and it invokes an external command that produces pack files that the histedit should later consume (like an external amend, that histedit then needs to work on top of). Python pack stores solve this by allowing callers to mark the store for a refresh. Let's add the same logic for rust stores. Once pack files are gone we can delete this. This will be useful for the upcoming migration of treemanifest to Rust contentstore. Filelog usage of the Rust contentstore avoided this issue by recreating the entire contentstore object in certain situations, but refresh seems useful and less expensive. Reviewed By: quark-zju Differential Revision: D23657036 fbshipit-source-id: 7c6438024c3d642bd22256a8e58961a6ee4bc867 |
||
|---|---|---|
| .. | ||
| async-runtime | ||
| auth | ||
| backingstore | ||
| blackbox | ||
| bookmarkstore | ||
| cdatapack | ||
| clib | ||
| clidispatch | ||
| cliparser | ||
| commitcloudsubscriber | ||
| commitstore/bench-serialize | ||
| configparser | ||
| cpython-ext | ||
| dag | ||
| dev-logger | ||
| drawdag | ||
| edenapi | ||
| edenfs-client | ||
| encoding | ||
| fsinfo | ||
| fsyncglob | ||
| hg-http | ||
| hg-metrics | ||
| hgcommands | ||
| hgcommits | ||
| hgtime | ||
| http-client | ||
| indexedlog | ||
| linelog | ||
| lz4-pyframe | ||
| manifest | ||
| manifest-tree | ||
| metalog | ||
| mincode | ||
| minibench | ||
| minibytes | ||
| mpatch | ||
| mpatch-sys | ||
| mutationstore | ||
| nodemap | ||
| pathmatcher | ||
| procinfo | ||
| radixbuf | ||
| renderdag | ||
| revisionstore | ||
| revlogindex | ||
| spawn-ext | ||
| taggederror | ||
| taggederror-util | ||
| third-party | ||
| thrift-types | ||
| tracing-collector | ||
| treestate | ||
| types | ||
| util | ||
| version | ||
| vfs | ||
| vlqencoding | ||
| workingcopy | ||
| xdiff | ||
| xdiff-sys | ||
| zstdelta | ||
| zstore | ||
| CMakeLists.txt | ||
| 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).