schreter

Add a `Runtime` configuration where underlying types are abstracted

3

This depends on: - #204 The `Runtime` configuration should abstract: - timing - async executor - synchronization primitives - ... This will allow addressing further stuff, especially making tests deterministic...

Make tests deterministics

5

~This depends on https://github.com/datafuselabs/openraft/issues/204 and https://github.com/datafuselabs/openraft/issues/205.~ This depends on: - #204 - #205 Currently, tests use real-time timers, which quite often cause non-deterministic results and as a consequence test failures...

Also support replacing user IDs with names in Reviewable (Web-based GitHub review tool)

1

We are using this plugin with GitHub and it works well. However, almost 100% of code reviews in our team are done using Reviewable.io (via our internal instance at SAP...

Design for Rust object by-value passing to C++ and back

12

In our project which requires perfect C++/Rust integration (where we actually consume a Rust library in a large C++ project) we extended `cxx` crate to handle Rust by-value types, so...

Rust type aliases

7

In https://github.com/dtolnay/cxx/pull/1181, I published a tentative implementation for Rust type aliases. The problem to solve is the following: we have two bridges, one exporting the Rust type, the other declaring...

Update exception handling to use `std::exception_ptr`

7

This makes the interface between C++ exception handling and Rust `Result` cleaner and allows passing C++ exception from the inner C++ call to the outer C++ call via Rust's `CxxException`...

The intention is to provide support to re-import Rust types already exported elsewhere into other bridges, creating equivalence of `extern "Rust"` types on the C++ side. Currently, the support is...

Currently, there is no way to "communicate" between C++ bridges depending on each other except for static compile-time checks, which verify that the types indeed fulfil the requirements in the...

Design for custom exceptions

1

In our project, we need to control which exceptions get thrown into C++ code from our Rust callbacks (i.e., it can't be `rust::Error`, not even `std::exception`, it has to be...

Design for panic-via-exception handling (and vice versa)

3

In our project which requires perfect C++/Rust integration regarding error handling we extended `cxx` crate to handle panics as C++ exceptions as well. This works well, however, the panic is...