mirror of
https://github.com/matrix-org/matrix-rust-sdk.git
synced 2026-05-13 02:25:51 -04:00
4f28dd85bf
The `add_or_update_remote_event` method always returns `true`. This patch updates the method to return nothing, and cleans up the call sites accordingly. This patch also adds comments to clarify the code flow. The bool value returned by `add_or_update_remote_event` was supposed to be `false` if the event was duplicated. First off, as soon as the `Timeline` receives its events from the `EventCache` via `VectorDiff`, the `event_cache::Deduplicator` will take care of deduplication, so the `Timeline` won't have to handle that itself. Second, `add_or_update_remote_event` was sometimes removing an event, but it was re-inserting a new one immediately without returning `false`: it was never returning `false` because a new event was always added.
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.