enum InheritDeprecation {
    Yes,
    No,
}
Expand description

Whether to inherit deprecation flags for nested items. In most cases, we do want to inherit deprecation, because nested items rarely have individual deprecation attributes, and so should be treated as deprecated if their parent is. However, default generic parameters have separate deprecation attributes from their parents, so we do not wish to inherit deprecation in this case. For example, inheriting deprecation for T in Foo<T> would cause a duplicate warning arising from both Foo and T being deprecated.

Variants§

§

Yes

§

No

Implementations§

Trait Implementations§

Returns a copy of the value. Read more
Performs copy-assignment from source. Read more

Auto Trait Implementations§

Blanket Implementations§

Gets the TypeId of self. Read more
Immutably borrows from an owned value. Read more
Mutably borrows from an owned value. Read more

Returns the argument unchanged.

Calls U::from(self).

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

The resulting type after obtaining ownership.
Creates owned data from borrowed data, usually by cloning. Read more
Uses borrowed data to replace owned data, usually by cloning. Read more
The type returned in the event of a conversion error.
Performs the conversion.
The type returned in the event of a conversion error.
Performs the conversion.

Layout§

Note: Most layout information is completely unstable and may even differ between compilations. The only exception is types with certain repr(...) attributes. Please see the Rust Reference’s “Type Layout” chapter for details on type layout guarantees.

Size: 1 byte

Size for each variant:

  • Yes: 0 bytes
  • No: 0 bytes