From: "Gary Guo" <gary@garyguo.net>
To: "Benno Lossin" <lossin@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>
Cc: <rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 10/15] rust: pin-init: add `#[default_error(<type>)]` attribute to initializer macros
Date: Wed, 14 Jan 2026 18:53:35 +0000 [thread overview]
Message-ID: <DFOJFXOFPXAJ.S2X6PE9EMAG3@garyguo.net> (raw)
In-Reply-To: <20260114181934.1782470-11-lossin@kernel.org>
On Wed Jan 14, 2026 at 6:18 PM GMT, Benno Lossin wrote:
> The `#[default_error(<type>)]` attribute can be used to supply a default
> type as the error used for the `[pin_]init!` macros. This way one can
> easily define custom `try_[pin_]init!` variants that default to your
> project specific error type. Just write the following declarative macro:
>
> macro_rules! try_init {
> ($($args:tt)*) => {
> ::pin_init::init!(
> #[default_error(YourCustomErrorType)]
> $($args)*
> )
> }
> }
>
> Tested-by: Andreas Hindborg <a.hindborg@kernel.org>
> Signed-off-by: Benno Lossin <lossin@kernel.org>
> ---
> Changes in v3: none
> Changes in v2:
> * improve error handling
> * improve parsing and default error evaluation
> ---
> rust/pin-init/internal/src/init.rs | 42 ++++++++++++++++++++++++++++--
> 1 file changed, 40 insertions(+), 2 deletions(-)
>
> diff --git a/rust/pin-init/internal/src/init.rs b/rust/pin-init/internal/src/init.rs
> index b0eb66224341..5a66016bdf33 100644
> --- a/rust/pin-init/internal/src/init.rs
> +++ b/rust/pin-init/internal/src/init.rs
> @@ -8,12 +8,13 @@
> parse_quote,
> punctuated::Punctuated,
> spanned::Spanned,
> - token, Block, Expr, ExprCall, ExprPath, Ident, Path, Token, Type,
> + token, Attribute, Block, Expr, ExprCall, ExprPath, Ident, Path, Token, Type,
> };
>
> use crate::diagnostics::{DiagCtxt, ErrorGuaranteed};
>
> pub(crate) struct Initializer {
> + attrs: Vec<InitializerAttribute>,
> this: Option<This>,
> path: Path,
> brace_token: token::Brace,
> @@ -54,8 +55,17 @@ fn ident(&self) -> Option<&Ident> {
> }
> }
>
> +enum InitializerAttribute {
> + DefaultError(DefaultErrorAttribute),
> +}
> +
> +struct DefaultErrorAttribute {
> + ty: Type,
> +}
Given the size of the struct, I would actually just make this `Box<Type>`
instead of suppressing the clippy warning in the last patch.
Otherwise this looks good to me.
Reviewed-by: Gary Guo <gary@garyguo.net>
> +
> pub(crate) fn expand(
> Initializer {
> + attrs,
> this,
> path,
> brace_token,
> @@ -69,7 +79,16 @@ pub(crate) fn expand(
> ) -> Result<TokenStream, ErrorGuaranteed> {
> let error = error.map_or_else(
> || {
> - if let Some(default_error) = default_error {
> + if let Some(default_error) = attrs.iter().fold(None, |acc, attr| {
> + #[expect(irrefutable_let_patterns)]
> + if let InitializerAttribute::DefaultError(DefaultErrorAttribute { ty }) = attr {
> + Some(ty.clone())
> + } else {
> + acc
> + }
> + }) {
> + default_error
> + } else if let Some(default_error) = default_error {
> syn::parse_str(default_error).unwrap()
> } else {
> dcx.error(brace_token.span.close(), "expected `? <type>` after `}`");
> @@ -358,6 +377,7 @@ fn make_field_check(
>
> impl Parse for Initializer {
> fn parse(input: syn::parse::ParseStream<'_>) -> syn::Result<Self> {
> + let attrs = input.call(Attribute::parse_outer)?;
> let this = input.peek(Token![&]).then(|| input.parse()).transpose()?;
> let path = input.parse()?;
> let content;
> @@ -389,7 +409,19 @@ fn parse(input: syn::parse::ParseStream<'_>) -> syn::Result<Self> {
> .peek(Token![?])
> .then(|| Ok::<_, syn::Error>((input.parse()?, input.parse()?)))
> .transpose()?;
> + let attrs = attrs
> + .into_iter()
> + .map(|a| {
> + if a.path().is_ident("default_error") {
> + a.parse_args::<DefaultErrorAttribute>()
> + .map(InitializerAttribute::DefaultError)
> + } else {
> + Err(syn::Error::new_spanned(a, "unknown initializer attribute"))
> + }
> + })
> + .collect::<Result<Vec<_>, _>>()?;
> Ok(Self {
> + attrs,
> this,
> path,
> brace_token,
> @@ -400,6 +432,12 @@ fn parse(input: syn::parse::ParseStream<'_>) -> syn::Result<Self> {
> }
> }
>
> +impl Parse for DefaultErrorAttribute {
> + fn parse(input: syn::parse::ParseStream<'_>) -> syn::Result<Self> {
> + Ok(Self { ty: input.parse()? })
> + }
> +}
> +
> impl Parse for This {
> fn parse(input: syn::parse::ParseStream<'_>) -> syn::Result<Self> {
> Ok(Self {
next prev parent reply other threads:[~2026-01-14 18:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 18:18 [PATCH v3 00/15] `syn` rewrite of pin-init Benno Lossin
2026-01-14 18:18 ` [PATCH v3 01/15] rust: pin-init: remove `try_` versions of the initializer macros Benno Lossin
2026-01-14 18:18 ` [PATCH v3 02/15] rust: pin-init: allow the crate to refer to itself as `pin-init` in doc tests Benno Lossin
2026-01-14 18:18 ` [PATCH v3 03/15] rust: pin-init: add `syn` dependency and remove `proc-macro[2]` and `quote` workarounds Benno Lossin
2026-01-14 18:18 ` [PATCH v3 04/15] rust: pin-init: internal: add utility API for syn error handling Benno Lossin
2026-01-14 18:26 ` Gary Guo
2026-01-14 18:18 ` [PATCH v3 05/15] rust: pin-init: rewrite `derive(Zeroable)` and `derive(MaybeZeroable)` using `syn` Benno Lossin
2026-01-14 18:29 ` Gary Guo
2026-01-14 18:18 ` [PATCH v3 06/15] rust: pin-init: rewrite the `#[pinned_drop]` attribute macro " Benno Lossin
2026-01-14 18:34 ` Gary Guo
2026-01-14 18:18 ` [PATCH v3 07/15] rust: pin-init: rewrite `#[pin_data]` " Benno Lossin
2026-01-14 18:47 ` Gary Guo
2026-01-14 18:18 ` [PATCH v3 08/15] rust: pin-init: add `?Sized` bounds to traits in `#[pin_data]` macro Benno Lossin
2026-01-14 18:47 ` Gary Guo
2026-01-14 18:18 ` [PATCH v3 09/15] rust: pin-init: rewrite the initializer macros using `syn` Benno Lossin
2026-01-14 18:51 ` Gary Guo
2026-01-15 21:45 ` Tamir Duberstein
2026-01-15 22:43 ` Benno Lossin
2026-01-16 0:19 ` Tamir Duberstein
2026-01-16 9:28 ` Benno Lossin
2026-01-16 15:39 ` Tamir Duberstein
2026-01-16 16:37 ` Benno Lossin
2026-01-14 18:18 ` [PATCH v3 10/15] rust: pin-init: add `#[default_error(<type>)]` attribute to initializer macros Benno Lossin
2026-01-14 18:53 ` Gary Guo [this message]
2026-01-14 18:18 ` [PATCH v3 11/15] rust: init: use `#[default_error(err)]` for the " Benno Lossin
2026-01-14 18:18 ` [PATCH v3 12/15] rust: pin-init: internal: init: add support for attributes on initializer fields Benno Lossin
2026-01-14 18:57 ` Gary Guo
2026-01-14 18:18 ` [PATCH v3 13/15] rust: pin-init: internal: init: add escape hatch for referencing initialized fields Benno Lossin
2026-01-14 18:58 ` Gary Guo
2026-01-14 18:18 ` [PATCH v3 14/15] rust: pin-init: internal: init: simplify Zeroable safety check Benno Lossin
2026-01-14 18:58 ` Gary Guo
2026-01-14 18:18 ` [PATCH v3 15/15] MAINTAINERS: add Gary Guo to pin-init 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=DFOJFXOFPXAJ.S2X6PE9EMAG3@garyguo.net \
--to=gary@garyguo.net \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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
all inboxes | Powered by JetHome®