chore: fix clippy warnings

Author: link2xt

src/client.rs

@@ -59,7 +59,9 @@ impl<T: Read + Write + Unpin + fmt::Debug> AsMut<T> for Session<T> {
     }
 }
 
-/// An (unauthenticated) handle to talk to an IMAP server. This is what you get when first
+/// An (unauthenticated) handle to talk to an IMAP server.
+///
+/// This is what you get when first
 /// connecting. A succesfull call to [`Client::login`] or [`Client::authenticate`] will return a
 /// [`Session`] instance that provides the usual IMAP methods.
 // Both `Client` and `Session` deref to [`Connection`](struct.Connection.html), the underlying

src/types/fetch.rs

@@ -12,7 +12,9 @@ use crate::types::ResponseData;
 const DATE_TIME_FORMAT: &str = "%d-%b-%Y %H:%M:%S %z";
 
 /// An IMAP [`FETCH` response](https://tools.ietf.org/html/rfc3501#section-7.4.2) that contains
-/// data about a particular message. This response occurs as the result of a `FETCH` or `STORE`
+/// data about a particular message.
+///
+/// This response occurs as the result of a `FETCH` or `STORE`
 /// command, as well as by unilateral server decision (e.g., flag updates).
 #[derive(Debug)]
 pub struct Fetch {

src/types/mod.rs

@@ -105,6 +105,8 @@ pub type Uid = u32;
 /// messages which have greater UIDs.
 pub type Seq = u32;
 
+/// Message flags.
+///
 /// With the exception of [`Flag::Custom`], these flags are system flags that are pre-defined in
 /// [RFC 3501 section 2.3.2](https://tools.ietf.org/html/rfc3501#section-2.3.2). All system flags
 /// begin with `\` in the IMAP protocol.  Certain system flags (`\Deleted` and `\Seen`) have
@@ -217,6 +219,7 @@ mod quota;
 pub use self::quota::*;
 
 /// Responses that the server sends that are not related to the current command.
+///
 /// [RFC 3501](https://tools.ietf.org/html/rfc3501#section-7) states that clients need to be able
 /// to accept any response at any time. These are the ones we've encountered in the wild.
 ///