1 // Copyright 2012-2015 The Rust Project Developers. See the COPYRIGHT
2 // file at the top-level directory of this distribution and at
3 // http://rust-lang.org/COPYRIGHT.
5 // Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
6 // http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
7 // <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
8 // option. This file may not be copied, modified, or distributed
9 // except according to those terms.
11 //! Primitive traits and types representing basic properties of types.
13 //! Rust types can be classified in various useful ways according to
14 //! their intrinsic properties. These classifications are represented
17 #![stable(feature = "rust1", since = "1.0.0")]
24 /// Types that can be transferred across thread boundaries.
26 /// This trait is automatically implemented when the compiler determines it's
29 /// An example of a non-`Send` type is the reference-counting pointer
30 /// [`rc::Rc`][`Rc`]. If two threads attempt to clone [`Rc`]s that point to the same
31 /// reference-counted value, they might try to update the reference count at the
32 /// same time, which is [undefined behavior][ub] because [`Rc`] doesn't use atomic
33 /// operations. Its cousin [`sync::Arc`][arc] does use atomic operations (incurring
34 /// some overhead) and thus is `Send`.
36 /// See [the Nomicon](../../nomicon/send-and-sync.html) for more details.
38 /// [`Rc`]: ../../std/rc/struct.Rc.html
39 /// [arc]: ../../std/sync/struct.Arc.html
40 /// [ub]: ../../reference/behavior-considered-undefined.html
41 #[stable(feature = "rust1", since = "1.0.0")]
42 #[rustc_on_unimplemented = "`{Self}` cannot be sent between threads safely"]
43 pub unsafe auto trait Send {
47 #[stable(feature = "rust1", since = "1.0.0")]
48 impl<T: ?Sized> !Send for *const T { }
49 #[stable(feature = "rust1", since = "1.0.0")]
50 impl<T: ?Sized> !Send for *mut T { }
52 /// Types with a constant size known at compile time.
54 /// All type parameters have an implicit bound of `Sized`. The special syntax
55 /// `?Sized` can be used to remove this bound if it's not appropriate.
58 /// # #![allow(dead_code)]
60 /// struct Bar<T: ?Sized>(T);
62 /// // struct FooUse(Foo<[i32]>); // error: Sized is not implemented for [i32]
63 /// struct BarUse(Bar<[i32]>); // OK
66 /// The one exception is the implicit `Self` type of a trait. A trait does not
67 /// have an implicit `Sized` bound as this is incompatible with [trait object]s
68 /// where, by definition, the trait needs to work with all possible implementors,
69 /// and thus could be any size.
71 /// Although Rust will let you bind `Sized` to a trait, you won't
72 /// be able to use it to form a trait object later:
75 /// # #![allow(unused_variables)]
77 /// trait Bar: Sized { }
80 /// impl Foo for Impl { }
81 /// impl Bar for Impl { }
83 /// let x: &Foo = &Impl; // OK
84 /// // let y: &Bar = &Impl; // error: the trait `Bar` cannot
85 /// // be made into an object
88 /// [trait object]: ../../book/first-edition/trait-objects.html
89 #[stable(feature = "rust1", since = "1.0.0")]
91 #[rustc_on_unimplemented = "`{Self}` does not have a constant size known at compile-time"]
92 #[fundamental] // for Default, for example, which requires that `[T]: !Default` be evaluatable
97 /// Types that can be "unsized" to a dynamically-sized type.
99 /// For example, the sized array type `[i8; 2]` implements `Unsize<[i8]>` and
100 /// `Unsize<fmt::Debug>`.
102 /// All implementations of `Unsize` are provided automatically by the compiler.
104 /// `Unsize` is implemented for:
106 /// - `[T; N]` is `Unsize<[T]>`
107 /// - `T` is `Unsize<Trait>` when `T: Trait`
108 /// - `Foo<..., T, ...>` is `Unsize<Foo<..., U, ...>>` if:
110 /// - Foo is a struct
111 /// - Only the last field of `Foo` has a type involving `T`
112 /// - `T` is not part of the type of any other fields
113 /// - `Bar<T>: Unsize<Bar<U>>`, if the last field of `Foo` has type `Bar<T>`
115 /// `Unsize` is used along with [`ops::CoerceUnsized`][coerceunsized] to allow
116 /// "user-defined" containers such as [`rc::Rc`][rc] to contain dynamically-sized
117 /// types. See the [DST coercion RFC][RFC982] and [the nomicon entry on coercion][nomicon-coerce]
118 /// for more details.
120 /// [coerceunsized]: ../ops/trait.CoerceUnsized.html
121 /// [rc]: ../../std/rc/struct.Rc.html
122 /// [RFC982]: https://github.com/rust-lang/rfcs/blob/master/text/0982-dst-coercion.md
123 /// [nomicon-coerce]: ../../nomicon/coercions.html
124 #[unstable(feature = "unsize", issue = "27732")]
126 pub trait Unsize<T: ?Sized> {
130 /// Types whose values can be duplicated simply by copying bits.
132 /// By default, variable bindings have 'move semantics.' In other
143 /// // `x` has moved into `y`, and so cannot be used
145 /// // println!("{:?}", x); // error: use of moved value
148 /// However, if a type implements `Copy`, it instead has 'copy semantics':
151 /// // We can derive a `Copy` implementation. `Clone` is also required, as it's
152 /// // a supertrait of `Copy`.
153 /// #[derive(Debug, Copy, Clone)]
160 /// // `y` is a copy of `x`
162 /// println!("{:?}", x); // A-OK!
165 /// It's important to note that in these two examples, the only difference is whether you
166 /// are allowed to access `x` after the assignment. Under the hood, both a copy and a move
167 /// can result in bits being copied in memory, although this is sometimes optimized away.
169 /// ## How can I implement `Copy`?
171 /// There are two ways to implement `Copy` on your type. The simplest is to use `derive`:
174 /// #[derive(Copy, Clone)]
178 /// You can also implement `Copy` and `Clone` manually:
183 /// impl Copy for MyStruct { }
185 /// impl Clone for MyStruct {
186 /// fn clone(&self) -> MyStruct {
192 /// There is a small difference between the two: the `derive` strategy will also place a `Copy`
193 /// bound on type parameters, which isn't always desired.
195 /// ## What's the difference between `Copy` and `Clone`?
197 /// Copies happen implicitly, for example as part of an assignment `y = x`. The behavior of
198 /// `Copy` is not overloadable; it is always a simple bit-wise copy.
200 /// Cloning is an explicit action, `x.clone()`. The implementation of [`Clone`] can
201 /// provide any type-specific behavior necessary to duplicate values safely. For example,
202 /// the implementation of [`Clone`] for [`String`] needs to copy the pointed-to string
203 /// buffer in the heap. A simple bitwise copy of [`String`] values would merely copy the
204 /// pointer, leading to a double free down the line. For this reason, [`String`] is [`Clone`]
207 /// [`Clone`] is a supertrait of `Copy`, so everything which is `Copy` must also implement
208 /// [`Clone`]. If a type is `Copy` then its [`Clone`] implementation only needs to return `*self`
209 /// (see the example above).
211 /// ## When can my type be `Copy`?
213 /// A type can implement `Copy` if all of its components implement `Copy`. For example, this
214 /// struct can be `Copy`:
217 /// # #[allow(dead_code)]
224 /// A struct can be `Copy`, and [`i32`] is `Copy`, therefore `Point` is eligible to be `Copy`.
225 /// By contrast, consider
228 /// # #![allow(dead_code)]
230 /// struct PointList {
231 /// points: Vec<Point>,
235 /// The struct `PointList` cannot implement `Copy`, because [`Vec<T>`] is not `Copy`. If we
236 /// attempt to derive a `Copy` implementation, we'll get an error:
239 /// the trait `Copy` may not be implemented for this type; field `points` does not implement `Copy`
242 /// ## When *can't* my type be `Copy`?
244 /// Some types can't be copied safely. For example, copying `&mut T` would create an aliased
245 /// mutable reference. Copying [`String`] would duplicate responsibility for managing the
246 /// [`String`]'s buffer, leading to a double free.
248 /// Generalizing the latter case, any type implementing [`Drop`] can't be `Copy`, because it's
249 /// managing some resource besides its own [`size_of::<T>`] bytes.
251 /// If you try to implement `Copy` on a struct or enum containing non-`Copy` data, you will get
252 /// the error [E0204].
254 /// [E0204]: ../../error-index.html#E0204
256 /// ## When *should* my type be `Copy`?
258 /// Generally speaking, if your type _can_ implement `Copy`, it should. Keep in mind, though,
259 /// that implementing `Copy` is part of the public API of your type. If the type might become
260 /// non-`Copy` in the future, it could be prudent to omit the `Copy` implementation now, to
261 /// avoid a breaking API change.
263 /// ## Additional implementors
265 /// In addition to the [implementors listed below][impls],
266 /// the following types also implement `Copy`:
268 /// * Function item types (i.e. the distinct types defined for each function)
269 /// * Function pointer types (e.g. `fn() -> i32`)
270 /// * Array types, for all sizes, if the item type also implements `Copy` (e.g. `[i32; 123456]`)
271 /// * Tuple types, if each component also implements `Copy` (e.g. `()`, `(i32, bool)`)
272 /// * Closure types, if they capture no value from the environment
273 /// or if all such captured values implement `Copy` themselves.
274 /// Note that variables captured by shared reference always implement `Copy`
275 /// (even if the referent doesn't),
276 /// while variables captured by mutable reference never implement `Copy`.
278 /// [`Vec<T>`]: ../../std/vec/struct.Vec.html
279 /// [`String`]: ../../std/string/struct.String.html
280 /// [`Drop`]: ../../std/ops/trait.Drop.html
281 /// [`size_of::<T>`]: ../../std/mem/fn.size_of.html
282 /// [`Clone`]: ../clone/trait.Clone.html
283 /// [`String`]: ../../std/string/struct.String.html
284 /// [`i32`]: ../../std/primitive.i32.html
285 /// [impls]: #implementors
286 #[stable(feature = "rust1", since = "1.0.0")]
288 pub trait Copy : Clone {
292 /// Types for which it is safe to share references between threads.
294 /// This trait is automatically implemented when the compiler determines
295 /// it's appropriate.
297 /// The precise definition is: a type `T` is `Sync` if `&T` is
298 /// [`Send`][send]. In other words, if there is no possibility of
299 /// [undefined behavior][ub] (including data races) when passing
300 /// `&T` references between threads.
302 /// As one would expect, primitive types like [`u8`][u8] and [`f64`][f64]
303 /// are all `Sync`, and so are simple aggregate types containing them,
304 /// like tuples, structs and enums. More examples of basic `Sync`
305 /// types include "immutable" types like `&T`, and those with simple
306 /// inherited mutability, such as [`Box<T>`][box], [`Vec<T>`][vec] and
307 /// most other collection types. (Generic parameters need to be `Sync`
308 /// for their container to be `Sync`.)
310 /// A somewhat surprising consequence of the definition is that `&mut T`
311 /// is `Sync` (if `T` is `Sync`) even though it seems like that might
312 /// provide unsynchronized mutation. The trick is that a mutable
313 /// reference behind a shared reference (that is, `& &mut T`)
314 /// becomes read-only, as if it were a `& &T`. Hence there is no risk
317 /// Types that are not `Sync` are those that have "interior
318 /// mutability" in a non-thread-safe form, such as [`cell::Cell`][cell]
319 /// and [`cell::RefCell`][refcell]. These types allow for mutation of
320 /// their contents even through an immutable, shared reference. For
321 /// example the `set` method on [`Cell<T>`][cell] takes `&self`, so it requires
322 /// only a shared reference [`&Cell<T>`][cell]. The method performs no
323 /// synchronization, thus [`Cell`][cell] cannot be `Sync`.
325 /// Another example of a non-`Sync` type is the reference-counting
326 /// pointer [`rc::Rc`][rc]. Given any reference [`&Rc<T>`][rc], you can clone
327 /// a new [`Rc<T>`][rc], modifying the reference counts in a non-atomic way.
329 /// For cases when one does need thread-safe interior mutability,
330 /// Rust provides [atomic data types], as well as explicit locking via
331 /// [`sync::Mutex`][mutex] and [`sync::RwLock`][rwlock]. These types
332 /// ensure that any mutation cannot cause data races, hence the types
333 /// are `Sync`. Likewise, [`sync::Arc`][arc] provides a thread-safe
334 /// analogue of [`Rc`][rc].
336 /// Any types with interior mutability must also use the
337 /// [`cell::UnsafeCell`][unsafecell] wrapper around the value(s) which
338 /// can be mutated through a shared reference. Failing to doing this is
339 /// [undefined behavior][ub]. For example, [`transmute`][transmute]-ing
340 /// from `&T` to `&mut T` is invalid.
342 /// See [the Nomicon](../../nomicon/send-and-sync.html) for more
343 /// details about `Sync`.
345 /// [send]: trait.Send.html
346 /// [u8]: ../../std/primitive.u8.html
347 /// [f64]: ../../std/primitive.f64.html
348 /// [box]: ../../std/boxed/struct.Box.html
349 /// [vec]: ../../std/vec/struct.Vec.html
350 /// [cell]: ../cell/struct.Cell.html
351 /// [refcell]: ../cell/struct.RefCell.html
352 /// [rc]: ../../std/rc/struct.Rc.html
353 /// [arc]: ../../std/sync/struct.Arc.html
354 /// [atomic data types]: ../sync/atomic/index.html
355 /// [mutex]: ../../std/sync/struct.Mutex.html
356 /// [rwlock]: ../../std/sync/struct.RwLock.html
357 /// [unsafecell]: ../cell/struct.UnsafeCell.html
358 /// [ub]: ../../reference/behavior-considered-undefined.html
359 /// [transmute]: ../../std/mem/fn.transmute.html
360 #[stable(feature = "rust1", since = "1.0.0")]
362 #[rustc_on_unimplemented(
363 message="`{Self}` cannot be shared between threads safely",
364 label="`{Self}` cannot be shared between threads safely"
366 pub unsafe auto trait Sync {
367 // FIXME(estebank): once support to add notes in `rustc_on_unimplemented`
368 // lands in beta, and it has been extended to check whether a closure is
369 // anywhere in the requirement chain, extend it as such (#48534):
373 // note="`{Self}` cannot be shared safely, consider marking the closure `move`"
380 #[stable(feature = "rust1", since = "1.0.0")]
381 impl<T: ?Sized> !Sync for *const T { }
382 #[stable(feature = "rust1", since = "1.0.0")]
383 impl<T: ?Sized> !Sync for *mut T { }
387 #[stable(feature = "rust1", since = "1.0.0")]
388 impl<T:?Sized> Hash for $t<T> {
390 fn hash<H: Hasher>(&self, _: &mut H) {
394 #[stable(feature = "rust1", since = "1.0.0")]
395 impl<T:?Sized> cmp::PartialEq for $t<T> {
396 fn eq(&self, _other: &$t<T>) -> bool {
401 #[stable(feature = "rust1", since = "1.0.0")]
402 impl<T:?Sized> cmp::Eq for $t<T> {
405 #[stable(feature = "rust1", since = "1.0.0")]
406 impl<T:?Sized> cmp::PartialOrd for $t<T> {
407 fn partial_cmp(&self, _other: &$t<T>) -> Option<cmp::Ordering> {
408 Option::Some(cmp::Ordering::Equal)
412 #[stable(feature = "rust1", since = "1.0.0")]
413 impl<T:?Sized> cmp::Ord for $t<T> {
414 fn cmp(&self, _other: &$t<T>) -> cmp::Ordering {
419 #[stable(feature = "rust1", since = "1.0.0")]
420 impl<T:?Sized> Copy for $t<T> { }
422 #[stable(feature = "rust1", since = "1.0.0")]
423 impl<T:?Sized> Clone for $t<T> {
424 fn clone(&self) -> $t<T> {
429 #[stable(feature = "rust1", since = "1.0.0")]
430 impl<T:?Sized> Default for $t<T> {
431 fn default() -> $t<T> {
438 /// Zero-sized type used to mark things that "act like" they own a `T`.
440 /// Adding a `PhantomData<T>` field to your type tells the compiler that your
441 /// type acts as though it stores a value of type `T`, even though it doesn't
442 /// really. This information is used when computing certain safety properties.
444 /// For a more in-depth explanation of how to use `PhantomData<T>`, please see
445 /// [the Nomicon](../../nomicon/phantom-data.html).
447 /// # A ghastly note 👻👻👻
449 /// Though they both have scary names, `PhantomData` and 'phantom types' are
450 /// related, but not identical. A phantom type parameter is simply a type
451 /// parameter which is never used. In Rust, this often causes the compiler to
452 /// complain, and the solution is to add a "dummy" use by way of `PhantomData`.
456 /// ## Unused lifetime parameters
458 /// Perhaps the most common use case for `PhantomData` is a struct that has an
459 /// unused lifetime parameter, typically as part of some unsafe code. For
460 /// example, here is a struct `Slice` that has two pointers of type `*const T`,
461 /// presumably pointing into an array somewhere:
463 /// ```compile_fail,E0392
464 /// struct Slice<'a, T> {
470 /// The intention is that the underlying data is only valid for the
471 /// lifetime `'a`, so `Slice` should not outlive `'a`. However, this
472 /// intent is not expressed in the code, since there are no uses of
473 /// the lifetime `'a` and hence it is not clear what data it applies
474 /// to. We can correct this by telling the compiler to act *as if* the
475 /// `Slice` struct contained a reference `&'a T`:
478 /// use std::marker::PhantomData;
480 /// # #[allow(dead_code)]
481 /// struct Slice<'a, T: 'a> {
484 /// phantom: PhantomData<&'a T>,
488 /// This also in turn requires the annotation `T: 'a`, indicating
489 /// that any references in `T` are valid over the lifetime `'a`.
491 /// When initializing a `Slice` you simply provide the value
492 /// `PhantomData` for the field `phantom`:
495 /// # #![allow(dead_code)]
496 /// # use std::marker::PhantomData;
497 /// # struct Slice<'a, T: 'a> {
498 /// # start: *const T,
500 /// # phantom: PhantomData<&'a T>,
502 /// fn borrow_vec<'a, T>(vec: &'a Vec<T>) -> Slice<'a, T> {
503 /// let ptr = vec.as_ptr();
506 /// end: unsafe { ptr.offset(vec.len() as isize) },
507 /// phantom: PhantomData,
512 /// ## Unused type parameters
514 /// It sometimes happens that you have unused type parameters which
515 /// indicate what type of data a struct is "tied" to, even though that
516 /// data is not actually found in the struct itself. Here is an
517 /// example where this arises with [FFI]. The foreign interface uses
518 /// handles of type `*mut ()` to refer to Rust values of different
519 /// types. We track the Rust type using a phantom type parameter on
520 /// the struct `ExternalResource` which wraps a handle.
522 /// [FFI]: ../../book/first-edition/ffi.html
525 /// # #![allow(dead_code)]
526 /// # trait ResType { }
527 /// # struct ParamType;
528 /// # mod foreign_lib {
529 /// # pub fn new(_: usize) -> *mut () { 42 as *mut () }
530 /// # pub fn do_stuff(_: *mut (), _: usize) {}
532 /// # fn convert_params(_: ParamType) -> usize { 42 }
533 /// use std::marker::PhantomData;
536 /// struct ExternalResource<R> {
537 /// resource_handle: *mut (),
538 /// resource_type: PhantomData<R>,
541 /// impl<R: ResType> ExternalResource<R> {
542 /// fn new() -> ExternalResource<R> {
543 /// let size_of_res = mem::size_of::<R>();
544 /// ExternalResource {
545 /// resource_handle: foreign_lib::new(size_of_res),
546 /// resource_type: PhantomData,
550 /// fn do_stuff(&self, param: ParamType) {
551 /// let foreign_params = convert_params(param);
552 /// foreign_lib::do_stuff(self.resource_handle, foreign_params);
557 /// ## Ownership and the drop check
559 /// Adding a field of type `PhantomData<T>` indicates that your
560 /// type owns data of type `T`. This in turn implies that when your
561 /// type is dropped, it may drop one or more instances of the type
562 /// `T`. This has bearing on the Rust compiler's [drop check]
565 /// If your struct does not in fact *own* the data of type `T`, it is
566 /// better to use a reference type, like `PhantomData<&'a T>`
567 /// (ideally) or `PhantomData<*const T>` (if no lifetime applies), so
568 /// as not to indicate ownership.
570 /// [drop check]: ../../nomicon/dropck.html
571 #[lang = "phantom_data"]
572 #[stable(feature = "rust1", since = "1.0.0")]
573 pub struct PhantomData<T:?Sized>;
575 impls! { PhantomData }
578 #[stable(feature = "rust1", since = "1.0.0")]
579 unsafe impl<'a, T: Sync + ?Sized> Send for &'a T {}
580 #[stable(feature = "rust1", since = "1.0.0")]
581 unsafe impl<'a, T: Send + ?Sized> Send for &'a mut T {}
584 /// Compiler-internal trait used to determine whether a type contains
585 /// any `UnsafeCell` internally, but not through an indirection.
586 /// This affects, for example, whether a `static` of that type is
587 /// placed in read-only static memory or writable static memory.
589 unsafe auto trait Freeze {}
591 impl<T: ?Sized> !Freeze for UnsafeCell<T> {}
592 unsafe impl<T: ?Sized> Freeze for PhantomData<T> {}
593 unsafe impl<T: ?Sized> Freeze for *const T {}
594 unsafe impl<T: ?Sized> Freeze for *mut T {}
595 unsafe impl<'a, T: ?Sized> Freeze for &'a T {}
596 unsafe impl<'a, T: ?Sized> Freeze for &'a mut T {}
598 /// Types which can be moved out of a `Pin`.
600 /// The `Unpin` trait is used to control the behavior of the [`Pin`] type. If a
601 /// type implements `Unpin`, it is safe to move a value of that type out of the
604 /// This trait is automatically implemented for almost every type.
606 /// [`Pin`]: ../mem/struct.Pin.html
607 #[unstable(feature = "pin", issue = "49150")]
608 pub unsafe auto trait Unpin {}
610 /// Implementations of `Copy` for primitive types.
612 /// Implementations that cannot be described in Rust
613 /// are implemented in `SelectionContext::copy_clone_conditions()` in librustc.
619 macro_rules! impl_copy {
622 #[stable(feature = "rust1", since = "1.0.0")]
629 usize u8 u16 u32 u64 u128
630 isize i8 i16 i32 i64 i128
635 #[unstable(feature = "never_type", issue = "35121")]
638 #[stable(feature = "rust1", since = "1.0.0")]
639 impl<T: ?Sized> Copy for *const T {}
641 #[stable(feature = "rust1", since = "1.0.0")]
642 impl<T: ?Sized> Copy for *mut T {}
644 // Shared references can be copied, but mutable references *cannot*!
645 #[stable(feature = "rust1", since = "1.0.0")]
646 impl<'a, T: ?Sized> Copy for &'a T {}