Error::from is already a function taking 1 parameter,
there's no need to wrap it with `|e| Error::from(e)`.

Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
This commit is contained in:
Wolfgang Bumiller 2019-02-18 13:21:25 +01:00
parent 8fdef1a81c
commit fc7f03523c
4 changed files with 5 additions and 5 deletions

View File

@ -69,7 +69,7 @@ fn run() -> Result<(), Error> {
let acceptor = std::sync::Arc::new(tokio_tls::TlsAcceptor::from(acceptor));
let connections = listener
.incoming()
.map_err(|e| Error::from(e))
.map_err(Error::from)
.and_then(move |sock| acceptor.accept(sock).map_err(|e| e.into()))
.then(|r| match r {
// accept()s can fail here with an Err() when eg. the client rejects

View File

@ -43,12 +43,12 @@ impl HttpClient {
let future = client
.request(request)
.map_err(|e| Error::from(e))
.map_err(Error::from)
.and_then(|resp| {
let status = resp.status();
resp.into_body().concat2().map_err(|e| Error::from(e))
resp.into_body().concat2().map_err(Error::from)
.and_then(move |data| {
let text = String::from_utf8(data.to_vec()).unwrap();

View File

@ -179,7 +179,7 @@ fn proxy_protected_request(
let resp = hyper::client::Client::new()
.request(request)
.map_err(|e| Error::from(e))
.map_err(Error::from)
.map(|mut resp| {
resp.extensions_mut().insert(NoLogExtension());
resp

View File

@ -86,7 +86,7 @@ impl Iterator for ReadDir {
fn next(&mut self) -> Option<Self::Item> {
self.iter.next().map(|res| {
res.map(|entry| ReadDirEntry { entry, parent_fd: self.dir_fd })
.map_err(|e| Error::from(e))
.map_err(Error::from)
})
}
}