Skip to content

Commit 1e47250

Browse files
committed
as_ptr returns a read-only pointer
1 parent 6cc24f2 commit 1e47250

File tree

3 files changed

+18
-2
lines changed

3 files changed

+18
-2
lines changed

src/libcore/slice/mod.rs

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -359,6 +359,10 @@ impl<T> [T] {
359359
/// The caller must ensure that the slice outlives the pointer this
360360
/// function returns, or else it will end up pointing to garbage.
361361
///
362+
/// The caller must also ensure that the memory the pointer (non-transitively) points to
363+
/// is never written to (except inside an `UnsafeCell`). If you need to mutate
364+
/// the contents of the slice, use [`as_mut_ptr`].
365+
///
362366
/// Modifying the container referenced by this slice may cause its buffer
363367
/// to be reallocated, which would also make any pointers to it invalid.
364368
///
@@ -374,6 +378,8 @@ impl<T> [T] {
374378
/// }
375379
/// }
376380
/// ```
381+
///
382+
/// [`as_mut_ptr`]: #method.as_mut_ptr
377383
#[stable(feature = "rust1", since = "1.0.0")]
378384
#[inline]
379385
pub const fn as_ptr(&self) -> *const T {

src/libcore/str/mod.rs

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2188,7 +2188,12 @@ impl str {
21882188
/// [`u8`]. This pointer will be pointing to the first byte of the string
21892189
/// slice.
21902190
///
2191+
/// The caller must ensure that the memory the pointer points to
2192+
/// is never written to. If you need to mutate
2193+
/// the contents of the string slice, use [`as_mut_ptr`].
2194+
///
21912195
/// [`u8`]: primitive.u8.html
2196+
/// [`as_mut_ptr`]: #method.as_mut_ptr
21922197
///
21932198
/// # Examples
21942199
///

src/libstd/ffi/c_str.rs

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,9 @@ use crate::sys;
4343
/// `CString` implements a [`as_ptr`] method through the [`Deref`]
4444
/// trait. This method will give you a `*const c_char` which you can
4545
/// feed directly to extern functions that expect a nul-terminated
46-
/// string, like C's `strdup()`.
46+
/// string, like C's `strdup()`. Notice that [`as_ptr`] returns a
47+
/// read-only pointer; if the C code writes to it, that causes
48+
/// undefined behavior.
4749
///
4850
/// # Extracting a slice of the whole C string
4951
///
@@ -61,7 +63,7 @@ use crate::sys;
6163
///
6264
/// Once you have the kind of slice you need (with or without a nul
6365
/// terminator), you can call the slice's own
64-
/// [`as_ptr`][slice.as_ptr] method to get a raw pointer to pass to
66+
/// [`as_ptr`][slice.as_ptr] method to get a read-only raw pointer to pass to
6567
/// extern functions. See the documentation for that function for a
6668
/// discussion on ensuring the lifetime of the raw pointer.
6769
///
@@ -1043,6 +1045,9 @@ impl CStr {
10431045
///
10441046
/// **WARNING**
10451047
///
1048+
/// The returned pointer is read-only; writing to it (including passing it
1049+
/// to C code that writes to it) causes undefined behavior.
1050+
///
10461051
/// It is your responsibility to make sure that the underlying memory is not
10471052
/// freed too early. For example, the following code will cause undefined
10481053
/// behavior when `ptr` is used inside the `unsafe` block:

0 commit comments

Comments
 (0)