[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aAi8qnGjhHsQKvWc@pollux>
Date: Wed, 23 Apr 2025 12:10:50 +0200
From: Danilo Krummrich <dakr@...nel.org>
To: Tamir Duberstein <tamird@...il.com>
Cc: Andrew Ballance <andrewjballance@...il.com>,
Alice Ryhl <aliceryhl@...gle.com>, Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...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@...nel.org>,
Trevor Gross <tmgross@...ch.edu>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 0/4] rust: alloc: split `Vec::set_len` into
`Vec::{inc,dec}_len`
On Wed, Apr 16, 2025 at 01:15:39PM -0400, Tamir Duberstein wrote:
> This series is the product of a discussion[0] on the safety requirements
> of `set_len`.
With the following changes, applied to alloc-next, thanks!
* Temporarily add #[expect(unused)] to dec_len() to avoid a compiler warning.
- Danilo
Powered by blists - more mailing lists