diff options
| author | Graydon Hoare <graydon@mozilla.com> | 2011-07-27 23:43:17 -0700 |
|---|---|---|
| committer | Graydon Hoare <graydon@mozilla.com> | 2011-07-27 23:43:17 -0700 |
| commit | 2749ef5ede454cc55fb5408a1dac41c0845fdf96 (patch) | |
| tree | 003aa33817b67f956b920b82a757b9e3906410da | |
| parent | ed96d1042bb63a6441aa139b305a2565a4ef7c44 (diff) | |
Fix stale 'copy' occurrences to 'move' in comments.
| -rw-r--r-- | src/comp/middle/kind.rs | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/comp/middle/kind.rs b/src/comp/middle/kind.rs index ab6c4bcf980..9893eb7dde7 100644 --- a/src/comp/middle/kind.rs +++ b/src/comp/middle/kind.rs @@ -4,7 +4,7 @@ * Every type has a kind. Every type parameter has a set of kind-capabilities * saying which kind of type may be passed as the parameter. * -* The kinds are based on two capabilities: copy and send. These may each be +* The kinds are based on two capabilities: move and send. These may each be * present or absent, though only three of the four combinations can actually * occur: * @@ -26,7 +26,7 @@ * * Since this forms a lattice, we denote the capabilites in terms of a * worst-case requirement. That is, if your function needs to move-and-send -* (or copy) your T, you write fn<~T>(...). If you need to copy but not send, +* (or copy) your T, you write fn<~T>(...). If you need to move but not send, * you write fn<@T>(...). And if you need neither -- can work with any sort of * pinned data at all -- then you write fn<T>(...). * |
