---

yaml
---
r: 35316
b: refs/heads/master
c: 38ba2c4
h: refs/heads/master
v: v3

Author: brson

[refs]

@@ -1,5 +1,5 @@
 ---
-refs/heads/master: b52a4b412e515620c2c3ccbe8b7f8c7e0300f6ff
+refs/heads/master: 38ba2c4941ede8d999a0208c50f1ad077ba259da
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: eb8fd119c65c67f3b1b8268cc7341c22d39b7b61
 refs/heads/try: d324a424d8f84b1eb049b12cf34182bda91b0024

trunk/src/libcore/kinds.rs

@@ -1,9 +1,35 @@
-//! The kind traits
+/*!
+The kind traits
 
-#[lang="const"]
-pub trait Const {
-    // Empty.
-}
+Rust types can be classified in vairous useful ways according to
+intrinsic properties of the type. These classifications, often called
+'kinds', are represented as traits.
+
+They cannot be implemented by user code, but are instead implemented
+by the compiler automatically for the types to which they apply.
+
+The 4 kinds are
+
+* Copy - types that may be copied without allocation. This includes
+  scalar types and managed pointers, and exludes owned pointers. It
+  also excludes types that implement `Drop`.
+
+* Send - owned types and types containing owned types.  These types
+  may be transferred across task boundaries.
+
+* Const - types that are deeply immutable. Const types are used for
+  freezable data structures.
+
+* Owned - types that do not contain borrowed pointers. Note that this
+  meaning of 'owned' conflicts with 'owned pointers'. The two notions
+  of ownership are different.
+
+`Copy` types include both implicitly copyable types that the compiler
+will copy automatically and non-implicitly copyable types that require
+the `copy` keyword to copy. Types that do not implement `Copy` may
+instead implement `Clone`.
+
+*/
 
 #[lang="copy"]
 pub trait Copy {
@@ -15,6 +41,11 @@ pub trait Send {
     // Empty.
 }
 
+#[lang="const"]
+pub trait Const {
+    // Empty.
+}
+
 #[lang="owned"]
 pub trait Owned {
     // Empty.