[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<ME0P282MB4890C545F827111FCE2D2AA0CCEB2@ME0P282MB4890.AUSP282.PROD.OUTLOOK.COM>
Date: Wed, 22 May 2024 13:24:47 +0000
From: Xu Roland <mu001999@...look.com>
To: Alice Ryhl <aliceryhl@...gle.com>
CC: "ojeda@...nel.org" <ojeda@...nel.org>, "boqun.feng@...il.com"
<boqun.feng@...il.com>, "rust-for-linux@...r.kernel.org"
<rust-for-linux@...r.kernel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>
Subject:
回复: [PATCH] rust: kernel: make impl_has_work compatible with more complex generics
Alice Ryhl Wrote:
> Please provide a more complete commit description. What user motivates
> this change?
I sent two new emails but I thought I made something wrong cause It seems not consequent with this.
And I found this issue at https://github.com/Rust-for-Linux/linux/issues/1077
________________________________________
发件人: Alice Ryhl <aliceryhl@...gle.com>
发送时间: 2024年5月22日 20:37
收件人: mu001999
抄送: ojeda@...nel.org; boqun.feng@...il.com; rust-for-linux@...r.kernel.org; linux-kernel@...r.kernel.org
主题: Re: [PATCH] rust: kernel: make impl_has_work compatible with more complex generics
On Wed, May 22, 2024 at 2:27 PM mu001999 <mu001999@...look.com> wrote:
>
> Signed-off-by: mu001999 <mu001999@...look.com>
Please provide a more complete commit description. What user motivates
this change?
> impl_has_work! {
> - impl<T> HasWork<Self> for ClosureWork<T> { self.work }
> + impl{T} HasWork<Self> for ClosureWork<T> { self.work }
> }
I ended up doing something similar for the generics in some of the
linked list patches. Does anyone know if it's possible to support this
without giving up the <T> syntax?
Alice
Powered by blists - more mailing lists