[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ-ks9=wr84zoxsyncOu==BQUS+Y7Lc8CUgfgKwuJc9imu87rg@mail.gmail.com>
Date: Thu, 24 Apr 2025 09:49:18 -0400
From: Tamir Duberstein <tamird@...il.com>
To: Alice Ryhl <aliceryhl@...gle.com>
Cc: Danilo Krummrich <dakr@...nel.org>, Matthew Maurer <mmaurer@...gle.com>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 5/7] rust: alloc: add Vec::retain
On Thu, Apr 24, 2025 at 7:46 AM Alice Ryhl <aliceryhl@...gle.com> wrote:
>
> On Wed, Apr 23, 2025 at 02:14:11PM +0200, Danilo Krummrich wrote:
> > On 4/22/25 11:52 AM, Alice Ryhl wrote:
> > > Unfortunately this can't be a kunit test because it uses the upstream
> > > Rust implementation of Vec::retain as a comparison, which we can't call
> > > from a kunit test.
> >
> > Would it work from the rusttest target? We can use our kernel Vec type from
> > there, but I don't remember if we still can use std Vec from there.
>
> My guess is no, but I don't know for sure.
Isn't it possible to write a test without needing std's implementation?
Powered by blists - more mailing lists