e8278b5d68
Inspired by the changes in #1013 I was thinking about the use case for `sync_*` and how we handle error cases. Most notably while we give the callback the option to stop the loop, we don't really give an indication to the outside, how to interpret that cancellation: was there a failure? should we restart? Take e.g. a connectivity issue on the wire, we'd constantly loop and just `warn`, what you might or might not see. Even if you handle that in the `sync_with_result_callback` and thus break the loop, the outer caller now still doesn't know whether everything is honky dory or whether they should restart. This Changes reworks that area by having all the `sync` return `Result<(), Error>`, where `()` means it was ended by the inner callback (which in `sync()` never occurs) or `Error` is the error either the inner `result_callback` found or the that was coming from the `send` in the first place. Thus allowing us to e.g. back down to sync as it was a dead wire or restart it if there was only a temporary problem. Making all that a just a bit more "rust-y". |
||
|---|---|---|
| .. | ||
| appservice_autojoin | ||
| autojoin | ||
| command_bot | ||
| cross_signing_bootstrap | ||
| custom_events | ||
| emoji_verification | ||
| get_profiles | ||
| getting_started | ||
| image_bot | ||
| login | ||
| timeline | ||
| wasm_command_bot | ||
| README.md | ||
README.md
Matrix SDK Examples
In this folder you find examples for using the matrix-sdk (and its various components) to implement specific common features, each as a separate crate. You can run each of them from the root of the repository, mind you that _ becomes - and the crate names are prefixed with example-. So to run the image bot example you can do cargo run -p example-image-bot.