pub enum Bucket {
Respond,
Notify,
Ignore,
}Expand description
What the classifier decided this thread is for.
Three, not twelve — executive-ai-assistant settled on exactly this split
and docs/MAIL-UX-RESEARCH.md §2 records why a larger vocabulary makes the
boundaries fuzzier without making the triage better.
Variants§
Respond
Needs a direct answer from the user.
Notify
Worth knowing, needs no reply.
Ignore
Not worth responding to or tracking.
Implementations§
Trait Implementations§
impl Copy for Bucket
Source§impl<'de> Deserialize<'de> for Bucket
impl<'de> Deserialize<'de> for Bucket
Source§fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>where
__D: Deserializer<'de>,
fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>where
__D: Deserializer<'de>,
Deserialize this value from the given Serde deserializer. Read more
impl Eq for Bucket
impl StructuralPartialEq for Bucket
Auto Trait Implementations§
impl Freeze for Bucket
impl RefUnwindSafe for Bucket
impl Send for Bucket
impl Sync for Bucket
impl Unpin for Bucket
impl UnsafeUnpin for Bucket
impl UnwindSafe for Bucket
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Mutably borrows from an owned value. Read more