Andreas Molzer 71c39dea4d Argument type for mutable with_metadata_of (#75091) ... The method takes two pointer arguments: one `self` supplying the pointer value, and a second pointer supplying the metadata. The new parameter type more clearly reflects the actual requirements. The provenance of the metadata parameter is disregarded completely. Using a mutable pointer in the call site can be coerced to a const pointer while the reverse is not true. An example of the current use: ```rust // Manually taking an unsized object from a `ManuallyDrop` into another allocation. let val: &core::mem::ManuallyDrop<T> = …; let ptr = val as *const _ as *mut T; let ptr = uninit.as_ptr().with_metadata_of(ptr); ``` This could then instead be simplified to: ```rust // Manually taking an unsized object from a `ManuallyDrop` into another allocation. let val: &core::mem::ManuallyDrop<T> = …; let ptr = uninit.as_ptr().with_metadata_of(&**val); ```		2022-10-21 14:46:14 +02:00
..
benches	add a benchmark for slice_iter.copied().array_chunks()	2022-10-17 23:40:21 +02:00
primitive_docs	Add primitive documentation to libcore	2021-09-12 02:23:08 +00:00
src	Argument type for mutable with_metadata_of (#75091)	2022-10-21 14:46:14 +02:00
tests	Adjust transmute{,_copy} to be clearer about which of T and U is input vs output	2022-10-19 22:36:14 -07:00
Cargo.toml	Avoid use of rand::thread_rng in stdlib benchmarks	2022-05-02 00:08:21 -07:00