7ec2b0b555
While it's possible to share the content between different event types in the usual case some event types have slightly different contents if they are sent out as a to-device event vs a room message event. The canonical example for this are key verification events where the to-device version has a transaction id field but the room message version uses event relationships for the same purpose. This patch makes it possible for to-device events to have different content structs. Type aliases are used where a common struct can be used.
Ruma – Your home in Matrix.
A set of Rust crates (libraries) for interacting with the Matrix chat network.
Status
As of 2020-09-29, we support the vast majority of endpoints in all of the various Matrix APIs.
As long as they are still at version 0.x though, only the latest API revision is considered supported. This may change after 1.x releases.
Contributing
See CONTRIBUTING.md.
Minimum Rust version
Ruma currently requires Rust 1.43.0. In general, we will never require beta or nightly for crates.io releases of our crates, and we will try to avoid releasing crates that depend on features that were only just stabilized.
The exception to this is ruma-signatures (and hence ruma with the federation-api feature) since it depends on ring, which is only guaranteed to work on the latest stable.