From 3c44f87bee622ad892ee65553eb7b18782e2af36 Mon Sep 17 00:00:00 2001 From: Ivan Enderlin Date: Thu, 23 Feb 2023 16:39:39 +0100 Subject: [PATCH] doc(sdk): Simplify one documentation. --- crates/matrix-sdk/src/sliding_sync/mod.rs | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/crates/matrix-sdk/src/sliding_sync/mod.rs b/crates/matrix-sdk/src/sliding_sync/mod.rs index 9a242955d..3292ce7ea 100644 --- a/crates/matrix-sdk/src/sliding_sync/mod.rs +++ b/crates/matrix-sdk/src/sliding_sync/mod.rs @@ -978,12 +978,8 @@ impl SlidingSync { /// Handle the HTTP response. /// /// But which response? `v4::Response`, aka the Sliding Sync response, or - /// `SyncResponse` which still relies on `v3`? - /// Well that's tricky. We have both here, because this Sliding Sync - /// implementation is still experimental, and we didn't want to be too - /// invasive. Thus, `SyncResponse` doesn't support Sliding Sync yet. Hence - /// the fact this method handles both at the same time. It's not super - /// annoying but it was important to clarify that. + /// `SyncResponse`? We have both because `SyncResponse` doesn't support + /// Sliding Sync yet. #[instrument(skip_all, fields(views = views.len()))] async fn handle_response( &self,