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§
Implementations§
Trait Implementations§
source§impl Clone for InheritDeprecation
impl Clone for InheritDeprecation
source§fn clone(&self) -> InheritDeprecation
fn clone(&self) -> InheritDeprecation
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreAuto Trait Implementations§
impl RefUnwindSafe for InheritDeprecation
impl Send for InheritDeprecation
impl Sync for InheritDeprecation
impl Unpin for InheritDeprecation
impl UnwindSafe for InheritDeprecation
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
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 bytesNo
: 0 bytes