Benjamin Bouvier
af3ce4b32b
The (matrix-sdk-)common crate used the (matrix-sdk-)test crate only to benefit from the `async_test` proc macro, which is conveniently defined in another crate. My goal is to make `EventFactory`, at this point in the commit history, defined in the main SDK crate, available in the test crate. `EventFactory` makes use of some types defined in common, so there's a circular dependency at the moment. To split this circular dependency, I've changed the common crate to depend on the test-macro crate directly; now the test crate can depend on the common crate, and everybody's happy.
matrix-rust-sdk
matrix-rust-sdk is an implementation of a Matrix client-server library in Rust.
Project structure
The rust-sdk consists of multiple crates that can be picked at your convenience:
- matrix-sdk - High level client library, with batteries included, you're most likely interested in this.
- matrix-sdk-base - No (network) IO client state machine that can be used to embed a Matrix client in your project or build a full fledged network enabled client lib on top of it.
- matrix-sdk-crypto - No (network) IO encryption state machine that can be used to add Matrix E2EE support to your client or client library.
Minimum Supported Rust Version (MSRV)
These crates are built with the Rust language version 2021 and require a minimum compiler version of 1.70.
Status
The library is in an alpha state, things that are implemented generally work but the API will change in breaking ways.
If you are interested in using the matrix-sdk now is the time to try it out and provide feedback.
Bindings
Some crates of the matrix-rust-sdk can be embedded inside other
environments, like Swift, Kotlin, JavaScript, Node.js etc. Please,
explore the bindings/ directory to learn more.