Make UnsolicitedResponse non_exhaustive

That way, as we discover additional unilateral responses in the future,
we won't have to make a breaking change to add them.
This commit is contained in:
Jon Gjengset 2020-05-18 14:12:34 -04:00
parent 0c3ce7943d
commit cf4aed569b
No known key found for this signature in database
GPG key ID: 3CB1EC545A706318

View file

@ -211,6 +211,7 @@ pub use imap_proto::StatusAttribute;
/// Note that `Recent`, `Exists` and `Expunge` responses refer to the currently `SELECT`ed folder, /// Note that `Recent`, `Exists` and `Expunge` responses refer to the currently `SELECT`ed folder,
/// so the user must take care when interpreting these. /// so the user must take care when interpreting these.
#[derive(Debug, PartialEq, Eq)] #[derive(Debug, PartialEq, Eq)]
#[non_exhaustive]
pub enum UnsolicitedResponse { pub enum UnsolicitedResponse {
/// An unsolicited [`STATUS response`](https://tools.ietf.org/html/rfc3501#section-7.2.4). /// An unsolicited [`STATUS response`](https://tools.ietf.org/html/rfc3501#section-7.2.4).
Status { Status {