[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72k-BaJFzY7bBci3Xqj6UKXEibpu5fGuxa2rkSZdjjvyRg@mail.gmail.com>
Date: Tue, 22 Jul 2025 12:28:47 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Benno Lossin <lossin@...nel.org>
Cc: Shankari Anand <shankari.ak0208@...il.com>, linux-kernel@...r.kernel.org,
rust-for-linux@...r.kernel.org, Miguel Ojeda <ojeda@...nel.org>,
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>,
Andreas Hindborg <a.hindborg@...nel.org>, Alice Ryhl <aliceryhl@...gle.com>,
Trevor Gross <tmgross@...ch.edu>, Danilo Krummrich <dakr@...nel.org>
Subject: Re: [PATCH v4] rust: move ARef and AlwaysRefCounted to sync::aref
On Tue, Jul 22, 2025 at 11:33 AM Benno Lossin <lossin@...nel.org> wrote:
>
> `ARef` specifically is about supporting types that already have their
> own "built-in" reference counting. I'm not sure if built-in is the best
> word to describe that, some alternatives are inherent or internal.
Yeah, it is a bit ambiguous (e.g. it could also be understood as that
the code is always built as built-in, which is true currently).
> Maybe we can just expand the module level docs with:
>
> //! Internal Reference Counting Support.
That would be nice, yeah, please send a patch. I will use "Internal"
for the time being so that it matches what you have here. (Inherent
sounded also good to me.)
Thanks!
Cheers,
Miguel
Powered by blists - more mailing lists