rust-pyo3: retrieving the InnerRevlog of hg-cpython This allows PyO3-based code to use the InnerRevlog, access its shared data (core InnerRevlog), which will then allow, e.g., to retrieve references on the core Index. On the `hg-cpython` (`rusthg` crate, `rustext` Python extension module), we had to also build as a Rust library, and open up some accesses (see notably the public accessor for `inner`, the core `InnerRevlog`). Retrieving the Rust struct underlying a Python object defined by another extension module written in Rust is tricky because the Python type objects are duplicated in the extension modules, leading to failure of the normal type checking. See the doc-comment of `convert_cpython::extract_inner_revlog` for a complete explanation. To solve this, we import the Python type object of `rustext` (defined by `hg-cpython`) and perform a manual check. Checking the Python type is necessary, as PyO3 documentation clearly state that downcasting an object that has not the proper type is Undefined Behaviour. At this point, we do not have conversion facilities for exceptions (`PyErr` on both sides), hence the remaining unwraps).

     1

use pyo3::prelude::*;

     2

     3

mod convert_cpython;

     4

mod dagops;

     5

mod exceptions;

     6

mod revision;

     7

mod util;

     8

     9

#[pymodule]

    10

fn pyo3_rustext(py: Python<'_>, m: &Bound<'_, PyModule>) -> PyResult<()> {

    11

    m.add(

    12

        "__doc__",

    13

        "Mercurial core concepts - Rust implementation exposed via PyO3",

    14

    )?;

    15

    // the module's __name__ is pyo3_rustext, not mercurial.pyo3_rustext

    16

    // (at least at this point).

    17

    let name: String = m.getattr("__name__")?.extract()?;

    18

    let dotted_name = format!("mercurial.{}", name);

    19

    20

    m.add_submodule(&dagops::init_module(py, &dotted_name)?)?;

    21

    m.add("GraphError", py.get_type::<exceptions::GraphError>())?;

    22

    Ok(())

    23

}