[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72=fNWhgXDjTg_3j--3JYRb38iioUZtO=xydTo3ZQiivyA@mail.gmail.com>
Date: Sun, 18 Aug 2024 23:32:06 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Benno Lossin <benno.lossin@...ton.me>
Cc: Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...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@...sung.com>, Alice Ryhl <aliceryhl@...gle.com>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rust: types: improve `ForeignOwnable` documentation
On Tue, Jul 30, 2024 at 8:23 PM Benno Lossin <benno.lossin@...ton.me> wrote:
>
> There are no guarantees for the pointer returned by `into_foreign`.
> This is simply because there is no safety documentation stating any
> guarantees. Therefore dereferencing and all other operations for that
> pointer are not allowed in a general context (i.e. when the concrete
> type implementing the trait is not known).
> This might be confusing, therefore add normal documentation to state
> that there are no guarantees given for the pointer.
>
> Signed-off-by: Benno Lossin <benno.lossin@...ton.me>
Applied to `rust-next` -- thanks everyone!
Cheers,
Miguel
Powered by blists - more mailing lists