[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72=0Q2KJ_Rmnsa596fRA0E3tE4cZtG7W7DHU94=nWLMoSg@mail.gmail.com>
Date: Wed, 27 Mar 2024 11:49:41 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Boqun Feng <boqun.feng@...il.com>
Cc: Wedson Almeida Filho <wedsonaf@...il.com>, rust-for-linux@...r.kernel.org,
Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>, Andreas Hindborg <a.hindborg@...sung.com>,
Alice Ryhl <aliceryhl@...gle.com>, linux-kernel@...r.kernel.org,
Wedson Almeida Filho <walmeida@...rosoft.com>
Subject: Re: [PATCH v2 07/10] rust: alloc: update `VecExt` to take allocation flags
On Wed, Mar 27, 2024 at 4:48 AM Boqun Feng <boqun.feng@...il.com> wrote:
>
> /me likes this! ;-) Too bad `write_slice_cloned()` is not stablized:
>
> https://doc.rust-lang.org/core/mem/union.MaybeUninit.html#method.write_slice_cloned
For future reference, it will be called `clone_from_slice` soon (1.78):
https://doc.rust-lang.org/beta/core/mem/union.MaybeUninit.html#method.clone_from_slice
https://github.com/rust-lang/rust/issues/79995
This could be a "good first issue", i.e. to replace these if these get
stabilized (which seems likely).
Though that one has to account for panics -- it would be good to check
codegen if we do replace it.
Cheers,
Miguel
Powered by blists - more mailing lists