--- a/rust/README.rst Fri May 29 12:12:16 2020 +0200
+++ b/rust/README.rst Fri May 29 12:17:59 2020 +0200
@@ -36,36 +36,6 @@
One day we may use this environment variable to switch to new experimental
binding crates like a hypothetical ``HGWITHRUSTEXT=hpy``.
-Using the fastest ``hg status``
--------------------------------
-
-The code for ``hg status`` needs to conform to ``.hgignore`` rules, which are
-all translated into regex.
-
-In the first version, for compatibility and ease of development reasons, the
-Re2 regex engine was chosen until we figured out if the ``regex`` crate had
-similar enough behavior.
-
-Now that that work has been done, the default behavior is to use the ``regex``
-crate, that provides a significant performance boost compared to the standard
-Python + C path in many commands such as ``status``, ``diff`` and ``commit``,
-
-However, the ``Re2`` path remains slightly faster for our use cases and remains
-a better option for getting the most speed out of your Mercurial.
-
-If you want to use ``Re2``, you need to install ``Re2`` following Google's
-guidelines: https://github.com/google/re2/wiki/Install.
-Then, use ``HG_RUST_FEATURES=with-re2`` and
-``HG_RE2_PATH=system|<path to your re2 install>`` when building ``hg`` to
-signal the use of Re2. Using the local path instead of the "system" RE2 links
-it statically.
-
-For example::
-
- $ HG_RUST_FEATURES=with-re2 HG_RE2_PATH=system make PURE=--rust
- $ # OR
- $ HG_RUST_FEATURES=with-re2 HG_RE2_PATH=/path/to/re2 make PURE=--rust
-
Developing Rust
===============
@@ -114,14 +84,3 @@
$ cargo +nightly fmt
This requires you to have the nightly toolchain installed.
-
-Additional features
--------------------
-
-As mentioned in the section about ``hg status``, code paths using ``re2`` are
-opt-in.
-
-For example::
-
- $ cargo check --features with-re2
-