Rollup merge of #67519 - Mark-Simulacrum:any-unsafe, r=Centril
Document why Any is not an unsafe trait The added documentation is not public (i.e., not in a doc comment) but that seems appropriate for this sort of low-level detail. Fixes #62303
This commit is contained in:
commit
ce6f0b0a1e
@ -74,6 +74,16 @@ use crate::intrinsics;
|
||||
/// See the [module-level documentation][mod] for more details.
|
||||
///
|
||||
/// [mod]: index.html
|
||||
// This trait is not unsafe, though we rely on the specifics of it's sole impl's
|
||||
// `type_id` function in unsafe code (e.g., `downcast`). Normally, that would be
|
||||
// a problem, but because the only impl of `Any` is a blanket implementation, no
|
||||
// other code can implement `Any`.
|
||||
//
|
||||
// We could plausibly make this trait unsafe -- it would not cause breakage,
|
||||
// since we control all the implementations -- but we choose not to as that's
|
||||
// both not really necessary and may confuse users about the distinction of
|
||||
// unsafe traits and unsafe methods (i.e., `type_id` would still be safe to call,
|
||||
// but we would likely want to indicate as such in documentation).
|
||||
#[stable(feature = "rust1", since = "1.0.0")]
|
||||
pub trait Any: 'static {
|
||||
/// Gets the `TypeId` of `self`.
|
||||
|
Loading…
Reference in New Issue
Block a user