[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72niWTCTF=X=MYEe5xbF_N9-En=Uq5Jt_b2LvLRC7yKjLg@mail.gmail.com>
Date: Sun, 18 Feb 2024 21:23:49 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Alice Ryhl <aliceryhl@...gle.com>
Cc: Miguel Ojeda <ojeda@...nel.org>, Wedson Almeida Filho <wedsonaf@...il.com>,
Alex Gaynor <alex.gaynor@...il.com>, Boqun Feng <boqun.feng@...il.com>,
Gary Guo <gary@...yguo.net>, Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] rust: add reexports for macros
On Mon, Jan 29, 2024 at 3:58 PM Alice Ryhl <aliceryhl@...gle.com> wrote:
>
> Currently, all macros are reexported with #[macro_export] only, which
> means that to access `new_work!` from the workqueue, you need to import
> it from the path `kernel::new_work` instead of importing it from the
> workqueue module like all other items in the workqueue. By adding
> reexports of the macros, it becomes possible to import the macros from
> the correct modules.
>
> It's still possible to import the macros from the root, but I don't
> think we can do anything about that.
>
> There is no functional change. This is merely a code cleanliness
> improvement.
>
> Signed-off-by: Alice Ryhl <aliceryhl@...gle.com>
Applied to `rust-next` with the new `prelude`s removed and a slightly
reworded title -- thanks everyone!
(I also created a "good first issue" about other `prelude`s that can
be removed: https://github.com/Rust-for-Linux/linux/issues/1064)
Cheers,
Miguel
Powered by blists - more mailing lists