Matthias Krüger 0cd87148d9 Rollup merge of #103106 - saethlin:from_exposed_docs, r=thomcc ... Try to say that memory outside the AM is always exposed cc ``@Gankra`` ``@thomcc`` I want to confidently tell people that they can use `from_exposed_addr` to get a pointer for doing MMIO and/or other hardware interactions done with volatile reads/writes at particular addresses outside the Rust AM. Currently, the docs indicate that would be UB. With this change, now the docs indicate that this is intended to be a valid use of `from_exposed_addr`. r? ``@RalfJung``		2022-10-27 09:25:09 +02:00
..
alignment.rs	Print the precondition we violated, and visible through output capture	2022-10-26 22:09:17 -04:00
const_ptr.rs	Rollup merge of #103035 - saethlin:assert_unsafe_precondition3, r=thomcc	2022-10-27 09:25:08 +02:00
metadata.rs	Use ptr::metadata in <[T]>::len implementation	2022-08-21 15:19:32 +00:00
mod.rs	Rollup merge of #103106 - saethlin:from_exposed_docs, r=thomcc	2022-10-27 09:25:09 +02:00
mut_ptr.rs	Rollup merge of #103580 - lukas-code:guaranteed_ne, r=GuillaumeGomez	2022-10-27 08:30:58 +09:00
non_null.rs	Print the precondition we violated, and visible through output capture	2022-10-26 22:09:17 -04:00
unique.rs	Implement core::ptr::Unique on top of NonNull	2022-04-14 19:35:40 +02:00