From: Wei Liu <wei.liu@kernel.org>
To: Boqun Feng <boqun.feng@gmail.com>
Cc: "Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Wei Liu" <wei.liu@kernel.org>,
rust-for-linux@vger.kernel.org,
"Linux Kernel List" <linux-kernel@vger.kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>
Subject: Re: [PATCH] rust: kernel: drop repetition in offset_of macro
Date: Fri, 16 Dec 2022 23:30:34 +0000 [thread overview]
Message-ID: <Y5z/msA6FWH0Bgmq@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <Y5zt9PSUD6d1MTyZ@boqun-archlinux>
On Fri, Dec 16, 2022 at 02:15:16PM -0800, Boqun Feng wrote:
> On Fri, Dec 16, 2022 at 06:26:57PM +0000, Wedson Almeida Filho wrote:
> > On Fri, 16 Dec 2022 at 17:49, Wei Liu <wei.liu@kernel.org> wrote:
> > >
> > > It doesn't make sense to allow multiple fields to be specified in
> > > offset_of.
> >
> > Why do you say it doesn't make sense?
> >
> > Here's what I had in mind:
> > ```
> > struct Y {
> > z: u32
> > }
> > struct X {
> > y: Y
> > }
> > offset_of!(X, y.z)
>
> For me, it's not very obvious that "y.z" is multiples of token trees
> rather a single token tree ;-)
>
> Maybe some examples of the match pattern of macros can help people catch
> up faster? Like
>
> "y.z" => tt [y], tt [.], tt [z]
>
> I will defer to Gary or Bjorn for a better quick guide of Rust macros
> ;-)
>
What will be even better is someone please contribute such a macro to
libcore so that I don't have to replicate the code snippet everywhere.
:-)
I have a version somewhere, the second argument matches against ident,
which was definitely not as flexible as tt.
Thanks,
Wei.
next prev parent reply other threads:[~2022-12-16 23:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 17:49 [PATCH] rust: kernel: drop repetition in offset_of macro Wei Liu
2022-12-16 18:26 ` Wedson Almeida Filho
2022-12-16 22:15 ` Boqun Feng
2022-12-16 23:30 ` Wei Liu [this message]
2022-12-16 23:57 ` Miguel Ojeda
2022-12-16 23:08 ` Wei Liu
2022-12-16 23:15 ` Wei Liu
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=Y5z/msA6FWH0Bgmq@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
/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).