From kry|ov@r00t @end|ng |rom gm@||@com  Tue Apr  4 09:50:15 2023
From: kry|ov@r00t @end|ng |rom gm@||@com (Ivan Krylov)
Date: Tue, 4 Apr 2023 10:50:15 +0300
Subject: [Rd] Breaking Change in Rcomplex Layout?
In-Reply-To: <3787c02c-2f7a-96b7-3299-35734db89a0f@gmail.com>
References: <CAPZyOoLG7Bgt0D_Nz-pdBv5k0_SmpFN9UuFE1-mKQxX76L=21g@mail.gmail.com>
 <e8c052d6-50ae-002d-71ba-5e160b56d419@gmail.com>
 <CAPZyOoL7rLbLHwQMziADwg_Dy-UGNScdwi3wf_RawWyU2Y4v-Q@mail.gmail.com>
 <c90c269e-1fdd-b12d-263c-e8c4a92e08db@gmail.com>
 <CAPZyOo++tZ-ThaGq=Zj3HbiY-r3wH3x0jPOHKgWcJ9zU-FTYLA@mail.gmail.com>
 <3787c02c-2f7a-96b7-3299-35734db89a0f@gmail.com>
Message-ID: <20230404105015.2a1a65fa@Tarkus>

On Tue, 4 Apr 2023 09:31:33 +0200
Tomas Kalibera <tomas.kalibera at gmail.com> wrote:

> it also matters how Rust can handle anonymous nested structures, or
> what is the right mapping of the involved C types to Rust

It's worth mentioning that Rust's RFC 2102 [1] defines unnamed structs
and unions for the purpose of C interoperability, but it's not yet
implemented.

Would it help Rust's bindgen (and, potentially, other C declaration
parsers) if R could optionally give a name to the anonymous union
member, like it's done in Windows API [2]?

-- 
Best regards,
Ivan

[1] https://github.com/rust-lang/rust/issues/49804

[2] https://devblogs.microsoft.com/oldnewthing/20170907-00/?p=96956



[Rd] Breaking Change in Rcomplex Layout?
Ivan Krylov