On Fri, Oct 13, 2023 at 12:50 AM Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote: > > On Thu, Oct 12, 2023 at 03:15:12PM -0700, Ramon de C Valle wrote: > > > [1]: > > https://doc.rust-lang.org/nightly/unstable-book/language-features/cfi-encoding.html > > I'm sorry, but that looks like a comment from where I'm sitting :-( > Worst part is it being on a line of it's own and thus unrelated to > anything. > > This rust syntax is horrific.. I understand where you're coming from. I'm still getting used to Rust syntax. > > > > [2]: > > https://doc.rust-lang.org/book/ch19-04-advanced-types.html#using-the-newtype-pattern-for-type-safety-and-abstraction > > I don't speak enough rust to even begin following this :/ > > > [3]: Wrapping a type in a struct should achieve something similar even > > without using the cfi_encoding attribute since the encoding for structs in > > both are <length><name>, where <name> is <unscoped-name>. > > You're not talking about C, right? Both C and repr(C) Rust structs have this encoding, but I understand the problems with doing this in C since it doesn't have repr(transparent) structs so there would be a lot of casting back and forth. Maybe there is an alternative or this could be done for less used function pairs?
