[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72=sR2FiD3agm+GvaC7yT5t+bums9DGnkex8ybkdk=oNiw@mail.gmail.com>
Date: Wed, 21 Jan 2026 19:11:58 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Gary Guo <gary@...yguo.net>
Cc: Miguel Ojeda <ojeda@...nel.org>, Boqun Feng <boqun.feng@...il.com>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
Danilo Krummrich <dakr@...nel.org>, Tamir Duberstein <tamird@...il.com>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rust: disallow use of `CStr::as_ptr`
On Wed, Jan 21, 2026 at 6:33 PM Gary Guo <gary@...yguo.net> wrote:
>
> These are the methods that we want people to use? The "internal implementation"
> means that the use of `CStr::as_char()` is the internal implementation detail of
> `as_char_ptr` so it's okay. But nobody else should use it.
Yeah, not sure how I read that, sorry. And obviously we can't (easily)
add it to `core` one.
Cheers,
Miguel
Powered by blists - more mailing lists