about summary refs log tree commit diff
diff options
context:
space:
mode:
authorRalf Jung <post@ralfj.de>2022-05-28 18:15:04 +0200
committerRalf Jung <post@ralfj.de>2022-05-28 18:15:04 +0200
commit852777eff12bfc99b355e7c9ddd803d11cd795aa (patch)
treead2fb19fa4acf1d41071f18efc9239057ef6dcfe
parentad33519455c7f10bc5e7fdb7cc45ef6f1ccc51c4 (diff)
downloadrust-852777eff12bfc99b355e7c9ddd803d11cd795aa.tar.gz
rust-852777eff12bfc99b355e7c9ddd803d11cd795aa.zip
note to future self
-rw-r--r--library/core/src/ptr/mod.rs1
1 files changed, 1 insertions, 0 deletions
diff --git a/library/core/src/ptr/mod.rs b/library/core/src/ptr/mod.rs
index 93728f844dd..6b1e63e0cfa 100644
--- a/library/core/src/ptr/mod.rs
+++ b/library/core/src/ptr/mod.rs
@@ -26,6 +26,7 @@
 //!   some memory happens to exist at that address and gets deallocated. This corresponds to writing
 //!   your own allocator: allocating zero-sized objects is not very hard. The canonical way to
 //!   obtain a pointer that is valid for zero-sized accesses is [`NonNull::dangling`].
+//FIXME: mention `ptr::invalid` above, once it is stable.
 //! * All accesses performed by functions in this module are *non-atomic* in the sense
 //!   of [atomic operations] used to synchronize between threads. This means it is
 //!   undefined behavior to perform two concurrent accesses to the same location from different