From: Albin Babu Varghese <albinbabuvarghese20@gmail.com>
To: Benno Lossin <lossin@kernel.org>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
rust-for-linux@vger.kernel.org
Subject: Re: [[PATCH]] rust/list: replace unwrap() with ? in doctest examples
Date: Mon, 26 May 2025 21:12:22 -0400 [thread overview]
Message-ID: <aDURdsc1rAbIC40T@arch-box> (raw)
In-Reply-To: <DA6DJEG780UH.3FURKORQ8OY6U@kernel.org>
Thank you, Benno and Miguel, for your feedback
> Having thought about this more, I think this is fine. I don't know which
> extension function we would add to make this nicer.
If the code looks good, I’ll submit a v2 with updates to the subject line, commit
message, description and tag list.
---
Cheers,
Albin
next prev parent reply other threads:[~2025-05-27 1:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-25 22:59 [[PATCH]] rust/list: replace unwrap() with ? in doctest examples Albin Babu Varghese
2025-05-26 8:18 ` Benno Lossin
2025-05-26 10:33 ` Miguel Ojeda
2025-05-26 20:28 ` Benno Lossin
2025-05-27 1:12 ` Albin Babu Varghese [this message]
2025-05-27 0:53 ` Albin Babu Varghese
-- strict thread matches above, loose matches on Subject: below --
2025-05-25 22:34 Albin Babu Varghese
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=aDURdsc1rAbIC40T@arch-box \
--to=albinbabuvarghese20@gmail.com \
--cc=lossin@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rust-for-linux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.