Enum EmailHeaders

Source
pub enum EmailHeaders {
Show 102 variants AcceptLanguage, AlternateRecipient, ArchivedAt, AuthenticationResults, AutoSubmitted, AutoForwarded, Autosubmitted, Bcc, Cc, Comments, ContentIdentifier, ContentReturn, ContentType, ContentTransferEncoding, Conversion, ConversionWithLoss, DLExpansionHistory, Date, DeferredDelivery, DeliveryDate, DiscardedX400IPMSExtensions, DiscardedX400MTSExtensions, DiscloseRecipients, DispositionNotificationOptions, DispositionNotificationTo, DKIMSignature, DowngradedFinalRecipient, DowngradedInReplyTo, DowngradedMessageId, DowngradedOriginalRecipient, DowngradedReferences, Encoding, Encrypted, Expires, ExpiryDate, From, GenerateDeliveryReport, Importance, InReplyTo, IncompleteCopy, Keywords, Language, LatestDeliveryTime, ListArchive, ListHelp, ListId, ListOwner, ListPost, ListSubscribe, ListUnsubscribe, ListUnsubscribePost, MessageContext, MessageId, MessageType, MIMEType, MIMEVersion, MTPriority, Obsoletes, Organization, OriginalEncodedInformationTypes, OriginalFrom, OriginalMessageId, OriginalRecipient, OriginatorReturnAddress, OriginalSubject, PICSLabel, PreventNonDeliveryReport, Priority, Received, ReceivedSPF, References, ReplyBy, ReplyTo, RequireRecipientValidSince, ResentBcc, ResentCc, ResentDate, ResentFrom, ResentMessageId, ResentReplyTo, ResentSender, ResentTo, ReturnPath, Sender, Sensitivity, Solicitation, Subject, Supersedes, TLSReportDomain, TLSReportSubmitter, TLSRequired, To, VBRInfo, X400ContentIdentifier, X400ContentReturn, X400ContentType, X400MTSIdentifier, X400Originator, X400Received, X400Recipients, X400Trace, Unknown(String),
}
Expand description

§Email Headers

The headers that a email can contain. Reference: https://www.iana.org/assignments/message-headers/message-headers.xhtml

§Example

use neo_email::mail::Mail;
use neo_email::headers::EmailHeaders;
 
let raw_email = b"From: jean@nervio\nSubject: Hello\n\nHello, World!";
let mail = Mail::<Vec<u8>>::from_bytes(raw_email.to_vec()).unwrap();
let from = mail.headers.get(&EmailHeaders::From).unwrap();

Variants§

§

AcceptLanguage

§Accept-Language

The Accept-Language header field can be used by user agents to indicate the set of natural languages that are preferred in the response. Reference: https://www.iana.org/go/rfc4021

§

AlternateRecipient

§Alternate-Recipient

The Alternate-Recipient header field can be used to specify an alternative recipient for the message. Reference: https://www.iana.org/go/rfc4021

§

ArchivedAt

§Archived-At

The Archived-At header field can be used to specify the date and time at which the message was archived. Reference: https://www.iana.org/go/rfc5064

§

AuthenticationResults

§Authentication-Results

The Authentication-Results header field can be used to convey the results of message authentication checks. Reference: https://www.iana.org/go/rfc8601

§

AutoSubmitted

§Auto-Submitted

The Auto-Submitted header field can be used to indicate that the message was generated automatically. Reference: https://www.iana.org/go/rfc3834

§

AutoForwarded

§Autoforwarded

The Autoforwarded header field can be used to indicate that the message was automatically forwarded. Reference: https://www.iana.org/go/rfc4021

§

Autosubmitted

§Autosubmitted

The Autosubmitted header field can be used to indicate that the message was generated automatically. Reference: https://www.iana.org/go/rfc4021

§

Bcc

§Bcc

The Bcc header field can be used to specify recipients who are not to be included in the delivery of the message. Reference: https://www.iana.org/go/rfc5322

§

Cc

§Cc

The Cc header field can be used to specify recipients who are to receive copies of the message. Reference: https://www.iana.org/go/rfc5322

§

Comments

§Comments

The Comments header field can be used to provide additional information about the message. Reference: https://www.iana.org/go/rfc5322

§

ContentIdentifier

§Content-Identifier

The Content-Identifier header field can be used to specify a unique identifier for the message. Reference: https://www.iana.org/go/rfc4021

§

ContentReturn

§Content-Return

The Content-Return header field can be used to specify the return address for non-delivery reports. Reference: https://www.iana.org/go/rfc4021

§

ContentType

§Content-Type

The Content-Type header field can be used to specify the media type of the message content. Reference: https://www.iana.org/go/rfc4021

§

ContentTransferEncoding

§Content-Transfer-Encoding

The Content-Transfer-Encoding header field can be used to specify the encoding used for the message content. Reference: https://www.iana.org/go/rfc4021

§

Conversion

§Conversion

The Conversion header field can be used to specify the conversion information for the message. Reference: https://www.iana.org/go/rfc4021

§

ConversionWithLoss

§Conversion-With-Loss

The Conversion-With-Loss header field can be used to specify the conversion information for the message with loss. Reference: https://www.iana.org/go/rfc4021

§

DLExpansionHistory

§DL-Expansion-History

The DL-Expansion-History header field can be used to specify the expansion history of a distribution list. Reference: https://www.iana.org/go/rfc4021

§

Date

§Date

The Date header field can be used to specify the date and time at which the message was sent. Reference: https://www.iana.org/go/rfc5322

§

DeferredDelivery

§Deferred-Delivery

The Deferred-Delivery header field can be used to specify the date and time at which the message is to be delivered.

§

DeliveryDate

§Delivery-Date

The Delivery-Date header field can be used to specify the date and time at which the message was delivered.

§

DiscardedX400IPMSExtensions

§Discarded-X400-IPMS-Extensions

The Discarded-X400-IPMS-Extensions header field can be used to specify the IPMS extensions that were discarded.

§

DiscardedX400MTSExtensions

§Discarded-X400-MTS-Extensions

The Discarded-X400-MTS-Extensions header field can be used to specify the MTS extensions that were discarded. Reference: https://www.iana.org/go/rfc4021

§

DiscloseRecipients

§Disclose-Recipients

The Disclose-Recipients header field can be used to specify whether the recipients of the message are disclosed. Reference: https://www.iana.org/go/rfc4021

§

DispositionNotificationOptions

§Disposition-Notification-Options

The Disposition-Notification-Options header field can be used to specify the options for disposition notifications. Reference: https://www.iana.org/go/rfc4021

§

DispositionNotificationTo

§Disposition-Notification-To

The Disposition-Notification-To header field can be used to specify the recipient for disposition notifications. Reference: https://www.iana.org/go/rfc4021

§

DKIMSignature

§DKIM-Signature

The DKIM-Signature header field can be used to specify the DKIM signature for the message. Reference: https://www.iana.org/go/rfc6376

§

DowngradedFinalRecipient

§Downgraded-Final-Recipient

The Downgraded-Final-Recipient header field can be used to specify the final recipient of the message. Reference: https://www.iana.org/go/rfc6857

§

DowngradedInReplyTo

§Downgraded-In-Reply-To

The Downgraded-In-Reply-To header field can be used to specify the message that this message is a reply to. Reference: https://www.iana.org/go/rfc6857

§

DowngradedMessageId

§Downgraded-Message-Id

The Downgraded-Message-Id header field can be used to specify the message identifier of the message. Reference: https://www.iana.org/go/rfc6857

§

DowngradedOriginalRecipient

§Downgraded-Original-Recipient

The Downgraded-Original-Recipient header field can be used to specify the original recipient of the message. Reference: https://www.iana.org/go/rfc6857

§

DowngradedReferences

§Downgraded-References

The Downgraded-References header field can be used to specify the references for the message. Reference: https://www.iana.org/go/rfc6857

§

Encoding

§Encoding

The Encoding header field can be used to specify the encoding of the message. Reference: https://www.iana.org/go/rfc4021

§

Encrypted

§Encrypted

The Encrypted header field can be used to specify whether the message is encrypted. Reference: https://www.iana.org/go/rfc4021

§

Expires

§Expires

The Expires header field can be used to specify the expiration date of the message. Reference: https://www.iana.org/go/rfc4021

§

ExpiryDate

§Expiry-Date

The Expiry-Date header field can be used to specify the expiry date of the message. Reference: https://www.iana.org/go/rfc4021

§

From

§From

The From header field can be used to specify the author of the message. Reference: https://www.iana.org/go/rfc5322

§

GenerateDeliveryReport

§Generate-Delivery-Report

The Generate-Delivery-Report header field can be used to specify whether a delivery report should be generated. Reference: https://www.iana.org/go/rfc4021

§

Importance

§Importance

The Importance header field can be used to specify the importance of the message. Reference: https://www.iana.org/go/rfc4021

§

InReplyTo

§In-Reply-To

The In-Reply-To header field can be used to specify the message that this message is a reply to. Reference: https://www.iana.org/go/rfc5322

§Incomplete-Copy

The Incomplete-Copy header field can be used to specify that the message is an incomplete copy. Reference: https://www.iana.org/go/rfc4021

§

IncompleteCopy

§Keywords

The Keywords header field can be used to specify the keywords for the message. Reference: https://www.iana.org/go/rfc5322

§

Keywords

§Keywords

The Keywords header field can be used to specify the keywords for the message. Reference: https://www.iana.org/go/rfc5322

§

Language

§Language

The Language header field can be used to specify the language of the message. Reference: https://www.iana.org/go/rfc4021

§

LatestDeliveryTime

§Latest-Delivery-Time

The Latest-Delivery-Time header field can be used to specify the latest time at which the message should be delivered. Reference: https://www.iana.org/go/rfc4021

§

ListArchive

§List-Archive

The List-Archive header field can be used to specify the URI for the list archive. Reference: https://www.iana.org/go/rfc4021

§

ListHelp

§List-Help

The List-Help header field can be used to specify the URI for the list help. Reference: https://www.iana.org/go/rfc4021

§

ListId

§List-Id

The List-Id header field can be used to specify the identifier for the list. Reference: https://www.iana.org/go/rfc4021

§

ListOwner

§List-Owner

The List-Owner header field can be used to specify the owner of the list.

§

ListPost

§List-Post

The List-Post header field can be used to specify the URI for posting to the list. Reference: https://www.iana.org/go/rfc4021

§

ListSubscribe

§List-Subscribe

The List-Subscribe header field can be used to specify the URI for subscribing to the list. Reference: https://www.iana.org/go/rfc4021

§

ListUnsubscribe

§List-Unsubscribe

The List-Unsubscribe header field can be used to specify the URI for unsubscribing from the list. Reference: https://www.iana.org/go/rfc4021

§

ListUnsubscribePost

§List-Unsubscribe-Post

The List-Unsubscribe-Post header field can be used to specify the URI for unsubscribing from the list. Reference: https://www.iana.org/go/rfc8058

§

MessageContext

§Message-Context

The Message-Context header field can be used to specify the context of the message. Reference: https://www.iana.org/go/rfc4021

§

MessageId

§Message-Id

The Message-Id header field can be used to specify the identifier for the message. Reference: https://www.iana.org/go/rfc5322

§

MessageType

§Message-Type

The Message-Type header field can be used to specify the type of the message. Reference: https://www.iana.org/go/rfc4021

§

MIMEType

§MIME-Type

The MIME-Type header field can be used to specify the MIME type of the message. Reference: https://www.iana.org/go/rfc4021

§

MIMEVersion

§MIME-Version

The MIME-Version header field can be used to specify the MIME version of the message. Reference: https://www.iana.org/go/rfc4021

§

MTPriority

§MT-Priority

The MT-Priority header field can be used to specify the priority of the message. Reference: https://www.iana.org/go/rfc6758

§

Obsoletes

§Obsoletes

The Obsoletes header field can be used to specify the messages that this message obsoletes. Reference: https://www.iana.org/go/rfc4021

§

Organization

§Organization

The Organization header field can be used to specify the organization of the message. Reference: https://www.iana.org/go/rfc7681

§

OriginalEncodedInformationTypes

§Original-Encoded-Information-Types

The Original-Encoded-Information-Types header field can be used to specify the encoded information types for the message. Reference: https://www.iana.org/go/rfc4021

§

OriginalFrom

§Original-From

The Original-From header field can be used to specify the original author of the message. Reference: https://www.iana.org/go/rfc4021

§

OriginalMessageId

§Original-Message-Id

The Original-Message-Id header field can be used to specify the original message identifier of the message. Reference: https://www.iana.org/go/rfc4021

§

OriginalRecipient

§Original-Recipient

The Original-Recipient header field can be used to specify the original recipient of the message. Reference: https://www.iana.org/go/rfc3798

§

OriginatorReturnAddress

§Originator-Return-Address

The Originator-Return-Address header field can be used to specify the return address for non-delivery reports. Reference: https://www.iana.org/go/rfc4021

§

OriginalSubject

§Original-Subject

The Original-Subject header field can be used to specify the original subject of the message. Reference: https://www.iana.org/go/rfc4021

§

PICSLabel

§PICS-Label

The PICS-Label header field can be used to specify the PICS label for the message. Reference: https://www.iana.org/go/rfc4021

§

PreventNonDeliveryReport

§Prevent-NonDelivery-Report

The Prevent-NonDelivery-Report header field can be used to specify that non-delivery reports should not be generated. Reference: https://www.iana.org/go/rfc4021

§

Priority

§Priority

The Priority header field can be used to specify the priority of the message. Reference: https://www.iana.org/go/rfc4021

§

Received

§Received

The Received header field can be used to specify the date and time at which the message was received. Reference: https://www.iana.org/go/rfc5321

§

ReceivedSPF

§Received-SPF

The Received-SPF header field can be used to specify the results of the SPF check. Reference: https://www.iana.org/go/rfc7208

§

References

§References

The References header field can be used to specify the references for the message. Reference: https://www.iana.org/go/rfc5322

§

ReplyBy

§Reply-By

The Reply-By header field can be used to specify the date and time by which a reply is requested. Reference: https://www.iana.org/go/rfc4021

§

ReplyTo

§Reply-To

The Reply-To header field can be used to specify the address to which replies should be sent. Reference: https://www.iana.org/go/rfc5322

§

RequireRecipientValidSince

§Require-Recipient-Valid-Since

The Require-Recipient-Valid-Since header field can be used to specify the date and time at which the recipient was validated. Reference: https://www.iana.org/go/rfc7293

§

ResentBcc

§Resent-Bcc

The Resent-Bcc header field can be used to specify recipients who are not to be included in the delivery of the message. Reference: https://www.iana.org/go/rfc5322

§

ResentCc

§Resent-Cc

The Resent-Cc header field can be used to specify recipients who are to receive copies of the message. Reference: https://www.iana.org/go/rfc5322

§

ResentDate

§Resent-Date

The Resent-Date header field can be used to specify the date and time at which the message was resent. Reference: https://www.iana.org/go/rfc5322

§

ResentFrom

§Resent-From

The Resent-From header field can be used to specify the sender of the message. Reference: https://www.iana.org/go/rfc5322

§

ResentMessageId

§Resent-Message-Id

The Resent-Message-Id header field can be used to specify the message identifier of the message. Reference: https://www.iana.org/go/rfc5322

§

ResentReplyTo

§Resent-Reply-To

The Resent-Reply-To header field can be used to specify the reply-to address for the message. Reference: https://www.iana.org/go/rfc5322

§

ResentSender

§Resent-Sender

The Resent-Sender header field can be used to specify the sender of the message. Reference: https://www.iana.org/go/rfc5322

§

ResentTo

§Resent-To

The Resent-To header field can be used to specify the recipients of the message. Reference: https://www.iana.org/go/rfc5322

§

ReturnPath

§Return-Path

The Return-Path header field can be used to specify the return path for the message. Reference: https://www.iana.org/go/rfc5321

§

Sender

§Sender

The Sender header field can be used to specify the sender of the message. Reference: https://www.iana.org/go/rfc5322

§

Sensitivity

§Sensitivity

The Sensitivity header field can be used to specify the sensitivity of the message. Reference: https://www.iana.org/go/rfc4021

§

Solicitation

§Solicitation

The Solicitation header field can be used to specify the solicitation for the message. Reference: https://www.iana.org/go/rfc3865

§

Subject

§Subject

The Subject header field can be used to specify the subject of the message. Reference: https://www.iana.org/go/rfc5322

§

Supersedes

§Supersedes

The Supersedes header field can be used to specify the message that this message supersedes. Reference: https://www.iana.org/go/rfc4021

§

TLSReportDomain

§TLS-Report-Domain

The TLS-Report-Domain header field can be used to specify the domain for the TLS report. Reference: https://www.iana.org/go/rfc8460

§

TLSReportSubmitter

§TLS-Report-Domain

The TLS-Report-Domain header field can be used to specify the domain for the TLS report. Reference: https://www.iana.org/go/rfc8460

§

TLSRequired

§TLS-Required

The TLS-Required header field can be used to specify that TLS is required for the message. Reference: https://www.iana.org/go/rfc8689

§

To

§To

The To header field can be used to specify the recipients of the message. Reference: https://www.iana.org/go/rfc5322

§

VBRInfo

§VBR-Info

The VBR-Info header field can be used to specify the VBR information for the message. Reference: https://www.iana.org/go/rfc5518

§

X400ContentIdentifier

§X400-Content-Identifier

The X400-Content-Identifier header field can be used to specify the content identifier for the message. Reference: https://www.iana.org/go/rfc4021

§

X400ContentReturn

§X400-Content-Return

The X400-Content-Return header field can be used to specify the return address for non-delivery reports. Reference: https://www.iana.org/go/rfc4021

§

X400ContentType

§X400-Content-Type

The X400-Content-Type header field can be used to specify the content type of the message. Reference: https://www.iana.org/go/rfc4021

§

X400MTSIdentifier

§X400-MTS-Identifier

The X400-MTS-Identifier header field can be used to specify the MTS identifier for the message. Reference: https://www.iana.org/go/rfc4021

§

X400Originator

§X400-Originator

The X400-Originator header field can be used to specify the originator of the message. Reference: https://www.iana.org/go/rfc4021

§

X400Received

§X400-Received

The X400-Received header field can be used to specify the received information for the message. Reference: https://www.iana.org/go/rfc4021

§

X400Recipients

§X400-Recipients

The X400-Recipients header field can be used to specify the recipients of the message. Reference: https://www.iana.org/go/rfc4021

§

X400Trace

§X400-Trace

The X400-Trace header field can be used to specify the trace information for the message. Reference: https://www.iana.org/go/rfc4021

§

Unknown(String)

§Unknown

The Unknown header field can be used to specify an unknown header.

Implementations§

Source§

impl EmailHeaders

§Email Headers Implementation

This implementation is for the EmailHeaders enum.

Source

pub fn from_bytes(bytes: &[u8]) -> Result<Self, String>

§From Bytes

This function creates a new EmailHeaders from bytes.

Source

pub fn to_string(&self) -> &str

§To String

This function converts the email header to a string.

Source

pub fn from_string(s: &str) -> Self

§From String

This function creates a new EmailHeaders from a string.

Trait Implementations§

Source§

impl Clone for EmailHeaders

Source§

fn clone(&self) -> EmailHeaders

Returns a duplicate of the value. Read more
1.0.0 · Source§

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source. Read more
Source§

impl Debug for EmailHeaders

Source§

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter. Read more
Source§

impl<'de> Deserialize<'de> for EmailHeaders

Source§

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>
where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer. Read more
Source§

impl Display for EmailHeaders

Source§

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter. Read more
Source§

impl FromStr for EmailHeaders

Source§

type Err = Error

The associated error which can be returned from parsing.
Source§

fn from_str(s: &str) -> Result<Self, Self::Err>

Parses a string s to return a value of this type. Read more
Source§

impl Hash for EmailHeaders

Source§

fn hash<__H: Hasher>(&self, state: &mut __H)

Feeds this value into the given Hasher. Read more
1.3.0 · Source§

fn hash_slice<H>(data: &[Self], state: &mut H)
where H: Hasher, Self: Sized,

Feeds a slice of this type into the given Hasher. Read more
Source§

impl Ord for EmailHeaders

Source§

fn cmp(&self, other: &EmailHeaders) -> Ordering

This method returns an Ordering between self and other. Read more
1.21.0 · Source§

fn max(self, other: Self) -> Self
where Self: Sized,

Compares and returns the maximum of two values. Read more
1.21.0 · Source§

fn min(self, other: Self) -> Self
where Self: Sized,

Compares and returns the minimum of two values. Read more
1.50.0 · Source§

fn clamp(self, min: Self, max: Self) -> Self
where Self: Sized,

Restrict a value to a certain interval. Read more
Source§

impl PartialEq for EmailHeaders

Source§

fn eq(&self, other: &EmailHeaders) -> bool

Tests for self and other values to be equal, and is used by ==.
1.0.0 · Source§

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.
Source§

impl PartialOrd for EmailHeaders

Source§

fn partial_cmp(&self, other: &EmailHeaders) -> Option<Ordering>

This method returns an ordering between self and other values if one exists. Read more
1.0.0 · Source§

fn lt(&self, other: &Rhs) -> bool

Tests less than (for self and other) and is used by the < operator. Read more
1.0.0 · Source§

fn le(&self, other: &Rhs) -> bool

Tests less than or equal to (for self and other) and is used by the <= operator. Read more
1.0.0 · Source§

fn gt(&self, other: &Rhs) -> bool

Tests greater than (for self and other) and is used by the > operator. Read more
1.0.0 · Source§

fn ge(&self, other: &Rhs) -> bool

Tests greater than or equal to (for self and other) and is used by the >= operator. Read more
Source§

impl Serialize for EmailHeaders

Source§

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>
where __S: Serializer,

Serialize this value into the given Serde serializer. Read more
Source§

impl Eq for EmailHeaders

Source§

impl StructuralPartialEq for EmailHeaders

Auto Trait Implementations§

Blanket Implementations§

Source§

impl<T> Any for T
where T: 'static + ?Sized,

Source§

fn type_id(&self) -> TypeId

Gets the TypeId of self. Read more
Source§

impl<T> Borrow<T> for T
where T: ?Sized,

Source§

fn borrow(&self) -> &T

Immutably borrows from an owned value. Read more
Source§

impl<T> BorrowMut<T> for T
where T: ?Sized,

Source§

fn borrow_mut(&mut self) -> &mut T

Mutably borrows from an owned value. Read more
Source§

impl<T> CloneToUninit for T
where T: Clone,

Source§

unsafe fn clone_to_uninit(&self, dest: *mut u8)

🔬This is a nightly-only experimental API. (clone_to_uninit)
Performs copy-assignment from self to dest. Read more
Source§

impl<Q, K> Equivalent<K> for Q
where Q: Eq + ?Sized, K: Borrow<Q> + ?Sized,

Source§

fn equivalent(&self, key: &K) -> bool

Checks if this value is equivalent to the given key. Read more
Source§

impl<T> From<T> for T

Source§

fn from(t: T) -> T

Returns the argument unchanged.

Source§

impl<T> Instrument for T

Source§

fn instrument(self, span: Span) -> Instrumented<Self>

Instruments this type with the provided Span, returning an Instrumented wrapper. Read more
Source§

fn in_current_span(self) -> Instrumented<Self>

Instruments this type with the current Span, returning an Instrumented wrapper. Read more
Source§

impl<T, U> Into<U> for T
where U: From<T>,

Source§

fn into(self) -> U

Calls U::from(self).

That is, this conversion is whatever the implementation of From<T> for U chooses to do.

Source§

impl<T> IntoEither for T

Source§

fn into_either(self, into_left: bool) -> Either<Self, Self>

Converts self into a Left variant of Either<Self, Self> if into_left is true. Converts self into a Right variant of Either<Self, Self> otherwise. Read more
Source§

fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
where F: FnOnce(&Self) -> bool,

Converts self into a Left variant of Either<Self, Self> if into_left(&self) returns true. Converts self into a Right variant of Either<Self, Self> otherwise. Read more
Source§

impl<T> Pointable for T

Source§

const ALIGN: usize

The alignment of pointer.
Source§

type Init = T

The type for initializers.
Source§

unsafe fn init(init: <T as Pointable>::Init) -> usize

Initializes a with the given initializer. Read more
Source§

unsafe fn deref<'a>(ptr: usize) -> &'a T

Dereferences the given pointer. Read more
Source§

unsafe fn deref_mut<'a>(ptr: usize) -> &'a mut T

Mutably dereferences the given pointer. Read more
Source§

unsafe fn drop(ptr: usize)

Drops the object pointed to by the given pointer. Read more
Source§

impl<T> ToOwned for T
where T: Clone,

Source§

type Owned = T

The resulting type after obtaining ownership.
Source§

fn to_owned(&self) -> T

Creates owned data from borrowed data, usually by cloning. Read more
Source§

fn clone_into(&self, target: &mut T)

Uses borrowed data to replace owned data, usually by cloning. Read more
Source§

impl<T> ToString for T
where T: Display + ?Sized,

Source§

fn to_string(&self) -> String

Converts the given value to a String. Read more
Source§

impl<T, U> TryFrom<U> for T
where U: Into<T>,

Source§

type Error = Infallible

The type returned in the event of a conversion error.
Source§

fn try_from(value: U) -> Result<T, <T as TryFrom<U>>::Error>

Performs the conversion.
Source§

impl<T, U> TryInto<U> for T
where U: TryFrom<T>,

Source§

type Error = <U as TryFrom<T>>::Error

The type returned in the event of a conversion error.
Source§

fn try_into(self) -> Result<U, <U as TryFrom<T>>::Error>

Performs the conversion.
Source§

impl<V, T> VZip<V> for T
where V: MultiLane<T>,

Source§

fn vzip(self) -> V

Source§

impl<T> WithSubscriber for T

Source§

fn with_subscriber<S>(self, subscriber: S) -> WithDispatch<Self>
where S: Into<Dispatch>,

Attaches the provided Subscriber to this type, returning a WithDispatch wrapper. Read more
Source§

fn with_current_subscriber(self) -> WithDispatch<Self>

Attaches the current default Subscriber to this type, returning a WithDispatch wrapper. Read more
Source§

impl<T> DeserializeOwned for T
where T: for<'de> Deserialize<'de>,

Source§

impl<T> ErasedDestructor for T
where T: 'static,