#[non_exhaustive]pub enum Section {
Answer,
Authority,
Additional,
}Expand description
Which section of a message a record was read from.
It matters: RFC 6762 §8.2’s tiebreaker records live in the Authority section and are a proposal, while a conflicting record in any other section is a claim — §9’s conflict resolution and §8.2’s tiebreak are different rules with different outcomes, and telling them apart starts here.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.
Answer
Answer — what the message asserts.
Authority
Authority — for a probe query, the rdata the prober proposes to use (§8.2).
Additional
Additional — what the sender thinks the receiver will want next (§6.2).
Trait Implementations§
impl Copy for Section
impl Eq for Section
impl StructuralPartialEq for Section
Auto Trait Implementations§
impl Forget for Section
impl Freeze for Section
impl Move for Section
impl RefUnwindSafe for Section
impl Send for Section
impl Sync for Section
impl Unpin for Section
impl UnsafeUnpin for Section
impl UnwindSafe for Section
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