From: John Hubbard <jhubbard@nvidia.com>
To: "Philipp Stanner" <pstanner@redhat.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Maíra Canal" <mcanal@igalia.com>
Cc: "Asahi Lina" <lina@asahilina.net>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@samsung.com>,
"Matthew Wilcox" <willy@infradead.org>,
rust-for-linux@vger.kernel.org, linux-fsdevel@vger.kernel.org,
kernel-dev@igalia.com
Subject: Re: [PATCH v8 2/2] rust: xarray: Add an abstraction for XArray
Date: Thu, 21 Mar 2024 17:22:11 -0700 [thread overview]
Message-ID: <f0b1ca50-dd0c-447e-bf21-6e6cac2d3afb@nvidia.com> (raw)
In-Reply-To: <c8279ceb44cf430e039a66d67ac2aa1d75e7e285.camel@redhat.com>
On 3/19/24 2:32 AM, Philipp Stanner wrote:
...
>>
>>> + if ret < 0 {
>>> + Err(Error::from_errno(ret))
>>> + } else {
>>> + guard.dismiss();
>>> + Ok(id as usize)
>>> + }
>>
>> You could make this easier to read using to_result.
>>
>> to_result(ret)?;
>> guard.dismiss();
>> Ok(id as usize)
>
> My 2 cents, I'd go for classic kernel style:
>
>
> if ret < 0 {
> return Err(...);
> }
>
> guard.dismiss();
> Ok(id as usize)
>
Yes.
As a "standard" C-based kernel person who is trying to move into Rust
for Linux, I hereby invoke my Rust-newbie powers to confirm that the
"clasic kernel style" above goes into my head much faster and easier,
yes. :)
I hope I'm not violating any "this is how Rust idioms must be"
conventions. But if not, then all other things being equal, it is of
course a nice touch to make the code more readable to the rest of the
kernel folks.
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2024-03-22 0:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 23:57 [PATCH v8 0/2] rust: xarray: Add an abstraction for XArray Maíra Canal
2024-03-09 23:57 ` [PATCH v8 1/2] rust: types: add FOREIGN_ALIGN to ForeignOwnable Maíra Canal
2024-03-15 12:19 ` Benno Lossin
2024-03-09 23:57 ` [PATCH v8 2/2] rust: xarray: Add an abstraction for XArray Maíra Canal
2024-03-18 12:10 ` Alice Ryhl
2024-03-19 9:32 ` Philipp Stanner
2024-03-22 0:22 ` John Hubbard [this message]
2024-03-22 1:20 ` Boqun Feng
2024-03-22 1:34 ` John Hubbard
2024-03-26 7:41 ` Philipp Stanner
2024-03-26 12:23 ` Miguel Ojeda
2024-03-26 13:53 ` Philipp Stanner
2024-03-26 17:03 ` Miguel Ojeda
2024-03-26 12:16 ` Miguel Ojeda
2024-03-22 11:12 ` Benno Lossin
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=f0b1ca50-dd0c-447e-bf21-6e6cac2d3afb@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=kernel-dev@igalia.com \
--cc=lina@asahilina.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mcanal@igalia.com \
--cc=ojeda@kernel.org \
--cc=pstanner@redhat.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
--cc=willy@infradead.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).