[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72==6_Km_UYWaxxWw4gLS0g5yK5dQYvq+2xGTQvmm4aHyA@mail.gmail.com>
Date: Tue, 30 Jul 2024 22:22:41 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Alice Ryhl <aliceryhl@...gle.com>
Cc: Miguel Ojeda <ojeda@...nel.org>, Wedson Almeida Filho <wedsonaf@...il.com>,
Alex Gaynor <alex.gaynor@...il.com>, Russell King <linux@...linux.org.uk>,
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@...sung.com>,
Christian Schrefl <chrisi.schrefl@...il.com>, Jamie Cunliffe <Jamie.Cunliffe@....com>,
Sven Van Asbroeck <thesven73@...il.com>, linux-arm-kernel@...ts.infradead.org,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
patches@...ts.linux.dev
Subject: Re: [PATCH] rust: error: allow `useless_conversion` for 32-bit builds
On Tue, Jul 30, 2024 at 7:55 PM Alice Ryhl <aliceryhl@...gle.com> wrote:
>
> The formatting here is a bit weird. Perhaps we should swap the cfg and
> the comment?
Yeah, I don't like it either -- I reflexively did it because in the
safety series I am sending, there was a case where it would not notice
the `// SAFETY` comment if an attribute was placed afterwards.
But for blocks like this works fine, so it is not needed here, so we
can change it, even we may need to be inconsistent in a few places
about this, at least until it is fixed (assuming it is indeed a false
positive).
I created an issue in Clippy about it:
https://github.com/rust-lang/rust-clippy/issues/13189.
Thanks!
Cheers,
Miguel
Powered by blists - more mailing lists