facebook/sapling
1
1
Fork 0
mirror of https://github.com/facebook/sapling.git synced 2024-10-09 16:31:02 +03:00
Code Issues Projects Releases Wiki Activity
7c43ca7c6b
sapling/lib
History
Ryan Prince 573a8eb9cc fixing xdiff build on windows 
Summary: fixing xdiff build on windows

Reviewed By: quark-zju

Differential Revision: D7189839

fbshipit-source-id: ef05219d911af44f3546bc51fb74539d06b443b5
2018-04-13 21:51:23 -07:00
..
cdatapack hg: make sure platform_madvise_away returns -1 on Windows 2018-04-13 21:51:11 -07:00
clib hg: start using imported mman-win32 in the portability headers 2018-04-13 21:51:10 -07:00
linelog hg: basic support for building hg using buck 2018-04-13 21:50:58 -07:00
radixbuf radixbuf: avoid using unstable features in buck build 2018-04-13 21:51:12 -07:00
third-party fixing xdiff build on windows 2018-04-13 21:51:23 -07:00
vlqencoding vlqencoding: add read_vlq_at API that works for AsRef<[u8]> 2018-04-13 21:51:19 -07:00
README.md READMEs: tweaks based on feedback 2018-01-12 12:35:52 -08:00

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).