Open jbr opened 3 years ago
I have some code that implements this using wrapper types, but would really love for a trait like this to exist:
A proposed async-tls-acceptor crate that publishes this trait:
async-tls-acceptor
#[async_trait] pub trait Acceptor<Input>: Clone + Send + Sync + 'static where Input: AsyncRead + AsyncWrite + Send + Sync + Unpin + 'static, { type Output: AsyncRead + AsyncWrite + Send + Sync + Unpin + 'static; type Error: std::fmt::Debug + Send + Sync; async fn accept(&self, input: Input) -> Result<Self::Output, Self::Error>; }
The implementation for async-tls would be:
#[async_trait] impl<Input> Acceptor<Input> for async_tls::TlsAcceptor where Input: AsyncRead + AsyncWrite + Send + Sync + Unpin + 'static, { type Output = async_tls::TlsStream<Input>; type Error = std::io::Error; async fn accept(&self, input: Input) -> Result<Self::Output, Self::Error> { async_tls::TlsAcceptor::accept(&self, input).await } }
Would this be welcomed?
refs: https://github.com/async-email/async-native-tls/issues/27
I have some code that implements this using wrapper types, but would really love for a trait like this to exist:
A proposed
async-tls-acceptor
crate that publishes this trait:The implementation for async-tls would be:
Would this be welcomed?
refs: https://github.com/async-email/async-native-tls/issues/27