From 869e7162c4cb5d888155cb14f9c2fb57ea98d56e Mon Sep 17 00:00:00 2001 From: Anthony Ramine Date: Thu, 29 Apr 2021 11:48:46 +0200 Subject: [PATCH] Remove obsolete note in the docs The Stream implementationa also wants you to take care of managing capacity yourself. --- src/share.rs | 5 ----- 1 file changed, 5 deletions(-) diff --git a/src/share.rs b/src/share.rs index 0629106..108e4a6 100644 --- a/src/share.rs +++ b/src/share.rs @@ -125,11 +125,6 @@ pub struct StreamId(u32); /// See method level documentation for more details on receiving data. See /// [`FlowControl`] for more details on inbound flow control. /// -/// Note that this type implements [`Stream`], yielding the received data frames. -/// When this implementation is used, the capacity is immediately released when -/// the data is yielded. It is recommended to only use this API when the data -/// will not be retained in memory for extended periods of time. -/// /// [`client::ResponseFuture`]: client/struct.ResponseFuture.html /// [`server::Connection`]: server/struct.Connection.html /// [`FlowControl`]: struct.FlowControl.html