From: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-rust@nongnu.org,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH] rust: temporarily disable double_parens check
Date: Fri, 10 Oct 2025 15:23:17 +0300 [thread overview]
Message-ID: <CAAjaMXaPv+hENfLuZUeLEOjakuw7dOTLQCeaUbuveZW4Y_2PBQ@mail.gmail.com> (raw)
In-Reply-To: <20251009211208.643222-1-pbonzini@redhat.com>
On Fri, Oct 10, 2025 at 12:12 AM Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> It is showing in the output of the bits! macro and not easy to fix there
> (at least not without making the macro more complex). Disable it for
> now.
>
> Link: https://github.com/rust-lang/rust-clippy/issues/15852
> Reported-by: Richard Henderson <richard.henderson@linaro.org>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
How about putting it in the macro expansion instead of globally allowing it?
macro_rules! foo {
($a:expr, $b:expr, $c:expr, $d:expr) => {
#[allow(clippy::double_parens)]
InterruptMask(((($a.union($b).union($c).union($d))).into_bits()) as u32)
}
}
Why is the double parenthesis needed here by the way? It's a method chain
> rust/Cargo.toml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/rust/Cargo.toml b/rust/Cargo.toml
> index 783e626802c..4f98b2c03d3 100644
> --- a/rust/Cargo.toml
> +++ b/rust/Cargo.toml
> @@ -109,6 +109,9 @@ used_underscore_binding = "deny"
> # nice to have, but cannot be enabled yet
> #wildcard_imports = "deny" # still have many bindings::* imports
>
> +# https://github.com/rust-lang/rust-clippy/issues/15852
> +double_parens = "allow"
> +
> # these may have false positives
> #option_if_let_else = "deny"
> cognitive_complexity = "deny"
> --
> 2.51.0
>
>
next prev parent reply other threads:[~2025-10-10 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 21:12 [PATCH] rust: temporarily disable double_parens check Paolo Bonzini
2025-10-10 12:23 ` Manos Pitsidianakis [this message]
2025-10-10 14:12 ` Paolo Bonzini
2025-10-10 14:14 ` Manos Pitsidianakis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAjaMXaPv+hENfLuZUeLEOjakuw7dOTLQCeaUbuveZW4Y_2PBQ@mail.gmail.com \
--to=manos.pitsidianakis@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-rust@nongnu.org \
--cc=richard.henderson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).