---

yaml
---
r: 134607
b: refs/heads/try
c: 50d179d
h: refs/heads/master
i:
  134605: 85f9442
  134603: 50d18b8
  134599: 9fd8046
  134591: 2fff197
v: v3

Author: gamazeps

[refs]

@@ -2,7 +2,7 @@
 refs/heads/master: 58413c09cd52ea4005d6ea7733ba1fb3a8f36589
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: 437179ed8bf7f7672f84b19265df1ce569e70490
-refs/heads/try: 6a37692ecbb88cd9c3ae06a7ae9d619aa535719d
+refs/heads/try: 50d179d0016ea5f3a3c820a45cdaa6921f9fb14c
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b
 refs/heads/try2: 147ecfdd8221e4a4d4e090486829a06da1e0ca3c

branches/try/src/librustrt/c_str.rs

@@ -38,8 +38,9 @@ unnecessary amounts of allocations.
 
 Be carefull to remember that the memory is managed by C allocator API and not
 by Rust allocator API.
-That means that the CString pointers should only be freed with C allocator API
-if you intend to do that on your own.
+That means that the CString pointers should be freed with C allocator API
+if you intend to do that on your own, as the behaviour if you free them with
+Rust's allocator API is not well defined
 
 An example of creating and using a C string would be:
 
@@ -137,8 +138,8 @@ impl<S: hash::Writer> hash::Hash<S> for CString {
 
 impl CString {
     /// Create a C String from a pointer, with memory managed by C's allocator
-    /// API, so do not call it with a pointer to memory managed by Rust's
-    /// allocator API.
+    /// API, so avoid calling it with a pointer to memory managed by Rust's
+    /// allocator API, as the behaviour would not be well defined.
     ///
     ///# Failure
     ///
@@ -272,7 +273,7 @@ impl CString {
     /// forgotten, meaning that the backing allocation of this
     /// `CString` is not automatically freed if it owns the
     /// allocation. In this case, a user of `.unwrap()` should ensure
-    /// the allocation is freed, to avoid leaking memory. You have to
+    /// the allocation is freed, to avoid leaking memory. You should
     /// use libc's memory allocator in this case.
     ///
     /// Prefer `.as_ptr()` when just retrieving a pointer to the