[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72nEwr52e1O-+jGFdrNnVRN8imq=mt1Nyow9mwRaxSocSg@mail.gmail.com>
Date: Thu, 7 Nov 2024 13:59:38 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Rasmus Villemoes <ravi@...vas.dk>
Cc: FUJITA Tomonori <fujita.tomonori@...il.com>, anna-maria@...utronix.de,
frederic@...nel.org, tglx@...utronix.de, jstultz@...gle.com, sboyd@...nel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
rust-for-linux@...r.kernel.org, andrew@...n.ch, hkallweit1@...il.com,
tmgross@...ch.edu, ojeda@...nel.org, alex.gaynor@...il.com, gary@...yguo.net,
bjorn3_gh@...tonmail.com, benno.lossin@...ton.me, a.hindborg@...sung.com,
aliceryhl@...gle.com, arnd@...db.de
Subject: Re: [PATCH v5 6/7] rust: Add read_poll_timeout functions
On Thu, Nov 7, 2024 at 1:50 PM Rasmus Villemoes <ravi@...vas.dk> wrote:
>
> Would it be too much to hope for either a compiler flag or simply
> default behaviour for having the backing, static store of the file!()
> &str being guaranteed to be followed by a nul character? (Of course that
> nul should not be counted in the slice's length). That would in general
> increase interop with C code.
Definitely -- please see the "`c_stringify!`, `c_concat!`, `c_file!`
macros" item in:
https://github.com/Rust-for-Linux/linux/issues/514
Relatedly, for `Location`, there is "C string equivalents
(nul-terminated) for `core::panic::Location`.", with this ACP:
https://github.com/rust-lang/libs-team/issues/466
Cheers,
Miguel
Powered by blists - more mailing lists