Messages in this thread | | | From | Alice Ryhl <> | Date | Wed, 15 May 2024 11:47:02 +0200 | Subject | Re: [PATCH 2/2] rust: init: add re-initialization functions |
| |
On Sat, May 4, 2024 at 5:45 PM Benno Lossin <benno.lossin@proton.me> wrote: > > On 03.05.24 13:34, Alice Ryhl wrote: > > On Thu, Apr 25, 2024 at 11:34 PM Benno Lossin <benno.lossin@proton.me> wrote: > >> > >> Sometimes it is necessary to split allocation and initialization into > >> two steps. One such situation is when reusing existing allocations > >> obtained via `Box::drop_contents`. See [1] for an example. > >> In order to support this use case add `re_[pin_]init` functions to the > >> pin-init API. These functions operate on already allocated smart > >> pointers that contain `MaybeUninit<T>`. > >> > >> Signed-off-by: Benno Lossin <benno.lossin@proton.me> > >> Link: https://lore.kernel.org/rust-for-linux/f026532f-8594-4f18-9aa5-57ad3f5bc592@proton.me/ [1] > > > > I'm not a big fan of the name. Perhaps we can use a name similar to > > `Box::write`? > > Sure, what would be your suggestion? I can only think of `write_pinned`, > but no idea what to do for `impl Init<T>`...
write_init and write_pin_init?
| |