From: Andreas Hindborg <nmi@metaspace.dk>
To: Benno Lossin <y86-dev@protonmail.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Alice Ryhl" <alice@ryhl.io>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev
Subject: Re: [PATCH v3 04/13] rust: add pin-init API core
Date: Fri, 31 Mar 2023 10:16:56 +0200 [thread overview]
Message-ID: <871ql549lv.fsf@metaspace.dk> (raw)
In-Reply-To: <6c3985d3-6b81-df0e-5c22-12a0d8044119@protonmail.com>
Benno Lossin <y86-dev@protonmail.com> writes:
> On 30.03.23 15:05, Andreas Hindborg wrote:
>>> +//! [`Arc<T>`]: crate::sync::Arc
>>> +//! [`impl PinInit<Foo>`]: PinInit
>>> +//! [`impl PinInit<T, E>`]: PinInit
>>> +//! [`impl Init<T, E>`]: Init
>>> +//! [`Opaque`]: kernel::types::Opaque
>>> +//! [`pin_data`]: ::macros::pin_data
>>> +//! [`UniqueArc<T>`]: kernel::sync::UniqueArc
>>> +//! [`Box<T>`]: alloc::boxed::Box
>>> +
>>> +use core::{convert::Infallible, marker::PhantomData, mem::MaybeUninit};
>>> +
>>> +/// A pinned initializer for `T`.
>>
>> "An initializer for a pinned `T`" instead?
>
> To me this does not really make sense, since the type `T` cannot be
> pinned, only an instance can be. But maybe I should use the term
> `pin-initializer` instead.
I see. Could be "An initializer for a pinned instance of `T`" then. Just
to clarify that the initializer itself is not the thing that is pinned.
next prev parent reply other threads:[~2023-03-31 8:18 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 22:32 [PATCH v3 00/13] Rust pin-init API for pinned initialization of structs y86-dev
2023-03-29 22:32 ` [PATCH v3 01/13] rust: macros: add `quote!` macro y86-dev
2023-03-30 11:42 ` Andreas Hindborg
2023-03-30 12:01 ` Andreas Hindborg
2023-03-30 13:11 ` Gary Guo
2023-03-30 13:33 ` Alice Ryhl
2023-03-31 10:43 ` Andreas Hindborg
2023-03-29 22:32 ` [PATCH v3 02/13] rust: sync: add `assume_init` to `UniqueArc` y86-dev
2023-03-30 4:13 ` Wedson Almeida Filho
2023-03-30 12:18 ` Andreas Hindborg
2023-03-30 13:33 ` Alice Ryhl
2023-03-29 22:33 ` [PATCH v3 03/13] rust: types: add `Opaque::raw_get` y86-dev
2023-03-30 10:49 ` Gary Guo
2023-03-30 12:32 ` Andreas Hindborg
2023-03-30 13:33 ` Alice Ryhl
2023-03-29 22:33 ` [PATCH v3 04/13] rust: add pin-init API core y86-dev
2023-03-30 13:05 ` Andreas Hindborg
2023-03-30 15:46 ` Benno Lossin
2023-03-31 8:16 ` Andreas Hindborg [this message]
2023-03-30 13:17 ` Alice Ryhl
2023-03-30 13:33 ` Alice Ryhl
2023-03-30 14:16 ` Andreas Hindborg
2023-03-30 15:37 ` Benno Lossin
2023-03-30 15:36 ` Benno Lossin
2023-03-31 12:00 ` Andreas Hindborg
2023-03-29 22:33 ` [PATCH v3 05/13] rust: init: add initialization macros y86-dev
2023-03-30 14:21 ` Alice Ryhl
2023-03-30 15:38 ` Benno Lossin
2023-03-31 12:02 ` Andreas Hindborg
2023-03-29 22:33 ` [PATCH v3 06/13] rust: init/sync: add `InPlaceInit` trait to pin-initialize smart pointers y86-dev
2023-03-30 10:58 ` Gary Guo
2023-03-30 13:39 ` Andreas Hindborg
2023-03-30 14:37 ` Alice Ryhl
2023-03-30 15:28 ` Benno Lossin
2023-03-30 20:24 ` Alice Ryhl
2023-03-29 22:33 ` [PATCH v3 07/13] rust: init: add `PinnedDrop` trait and macros y86-dev
2023-03-30 11:01 ` Gary Guo
2023-03-30 15:41 ` Benno Lossin
2023-03-30 14:45 ` Alice Ryhl
2023-03-31 12:31 ` Andreas Hindborg
2023-03-29 22:33 ` [PATCH v3 08/13] rust: init: add `stack_pin_init!` macro y86-dev
2023-03-30 11:06 ` Gary Guo
2023-03-30 15:07 ` Alice Ryhl
2023-03-30 15:00 ` Alice Ryhl
2023-03-30 15:19 ` Benno Lossin
2023-03-30 20:28 ` Alice Ryhl
2023-03-31 12:43 ` Andreas Hindborg
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=871ql549lv.fsf@metaspace.dk \
--to=nmi@metaspace.dk \
--cc=alex.gaynor@gmail.com \
--cc=alice@ryhl.io \
--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=patches@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
--cc=y86-dev@protonmail.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
all inboxes | Powered by JetHome®