view CONTRIBUTING @ 51933:f2832de2a46c

interfaces: introduce and use a protocol class for the `bdiff` module

This is allowed by PEP 544[1], and we basically follow the example there.  The
class here is copied from `mercurial.pure.bdiff`, and the implementation
removed.

There are several modules that have a few different implementations, and the
implementation chosen is controlled by `HGMODULEPOLICY`.  The module is loaded
via `mercurial/policy.py`, and has been inferred by pytype as `Any` up to this
point.  Therefore it and PyCharm were blind to all functions on the module, and
their signatures.  Also, having multiple instances of the same module allows
their signatures to get out of sync.

Introducing a protocol class allows the loaded module that is stored in a
variable to be given type info, which cascades through the various places it is
used.  This change alters 11 *.pyi files, for example.  In theory, this would
also allow us to ensure the various implementations of the same module are kept
in alignment- simply import the module in a test module, attempt to pass it to a
function that uses the corresponding protocol as an argument, and run pytype on
it.

In practice, this doesn't work (yet).  PyCharm (erroneously) flags imported
modules being passed where a protocol class is used[2].  Pytype has problems the
other way- it fails to detect when a module that doesn't adhere to the protocol
is passed to a protocol argument.  The good news is that mypy properly detects
this case.  The bad news is that mypy spews a bunch of other errors when
importing even simple modules, like the various `bdiff` modules.  Therefore I'm
punting on the tests for now because the type info around a loaded module in
PyCharm is a clear win by itself.

[1] https://peps.python.org/pep-0544/#modules-as-implementations-of-protocols
[2] https://youtrack.jetbrains.com/issue/PY-58679/Support-modules-implementing-protocols

Our full contribution guidelines are in our wiki, please see:

https://www.mercurial-scm.org/wiki/ContributingChanges

If you just want a checklist to follow, you can go straight to

https://www.mercurial-scm.org/wiki/ContributingChanges#Submission_checklist

If you can't run the entire testsuite for some reason (it can be
difficult on Windows), please at least run `contrib/check-code.py` on
any files you've modified and run `python contrib/check-commit` on any
commits you've made (for example, `python contrib/check-commit
273ce12ad8f1` will report some style violations on a very old commit).