linux-kernel - Re: [PATCH] rust: kernel: make impl_has_work compatible with more complex generics

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAH5fLgiL7EdnzRL79x4zX0pXrtb8OjVkRib+qkoi=TyzHzEc4A@mail.gmail.com>
Date: Wed, 22 May 2024 14:37:19 +0200
From: Alice Ryhl <aliceryhl@...gle.com>
To: mu001999 <mu001999@...look.com>
Cc: ojeda@...nel.org, boqun.feng@...il.com, rust-for-linux@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: 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