Miguel Ojeda ab309b6e08 rust: avoid box_uninit_write feature ... Like commit 0903b9e2a4 ("rust: alloc: eschew `Box<MaybeUninit<T>>::write`"), but for the new `rbtree` and `alloc` code. That is, `feature(new_uninit)` [1] got partially stabilized [2] for Rust 1.82.0 (expected to be released on 2024-10-17), but it did not include `Box<MaybeUninit<T>>::write`, which got split into `feature(box_uninit_write)` [3]. To avoid relying on a new unstable feature, rewrite the `write` + `assume_init` pair manually. Link: https://github.com/rust-lang/rust/issues/63291 [1] Link: https://github.com/rust-lang/rust/pull/129401 [2] Link: https://github.com/rust-lang/rust/issues/129397 [3] Reviewed-by: Alice Ryhl <aliceryhl@google.com> Reviewed-by: Matt Gilbride <mattgilbride@google.com> Link: https://lore.kernel.org/r/20240904144229.18592-1-ojeda@kernel.org Signed-off-by: Miguel Ojeda <ojeda@kernel.org>		2024-09-04 23:11:31 +02:00
..
allocator.rs	slab, rust: extend kmalloc() alignment guarantees to remove Rust padding	2024-07-03 12:23:27 +02:00
box_ext.rs	rust: avoid box_uninit_write feature	2024-09-04 23:11:31 +02:00
vec_ext.rs	rust: avoid unused import warning in rusttest	2024-06-11 23:33:28 +02:00