pub trait WeakSpecialization: Sized {
// Required method
fn try_new_if_lifetime_free_weak() -> Option<Self>;
}alloc and unreliable only.Expand description
A extension trait for Specialization type for specializing one
completely unconstrained type to another completely unconstrained type.
§Reliability
While it is unlikely, there is still a possibility that the methods of this trait may return false negatives in future Rust versions.
The correctness of the results returned by the methods depends on the following:
- Documented behavior that if
TimplementsEq, twoRcs that point to the same allocation are always equal: https://doc.rust-lang.org/1.82.0/std/rc/struct.Rc.html#method.eq. - Undocumented behavior that the
Rc::partial_eqimplementation forT: Eqwill not usePartialEq::eqif bothRcs point to the same memory location. - The assumption that the undocumented short-circuit behavior described above will be retained for optimization purposes.
There is no formal guarantee that the undocumented behavior described above
will be retained. If the implementation changes in a future Rust version,
the function may return a false negative, that is, it may return false,
even though T implements the trait. However, the implementation guarantees
that a false positive result is impossible, i.e., the function will never
return true if T does not implement the trait in any future Rust version.
Details:
Required Methods§
Sourcefn try_new_if_lifetime_free_weak() -> Option<Self>
fn try_new_if_lifetime_free_weak() -> Option<Self>
Checks the types T1 and T2 for equality and returns the
specialization provider if types implement LifetimeFree and the types
are equal.
The LifetimeFree trait is not automatically derived for all
lifetime-free types. The library only implements it for standard library
types that do not have any lifetime parameters. This function uses
impls_lifetime_free to check wherever the unconstrained type
implements LifetimeFree trait or not.
Dyn Compatibility§
This trait is not dyn compatible.
In older versions of Rust, dyn compatibility was called "object safety", so this trait is not object safe.