search for: __bindgen_anon_1

...> code caused rustc compiler errors such as: > |error[E0560]: union `libR_sys::Rcomplex` has no field named `r` --> > extendr-api\src\robj\into_robj.rs:93:20 | 93 | Rcomplex { r: 0., i: 0. > } | ^ `libR_sys::Rcomplex` does not have this field | = note: > available fields are: `__bindgen_anon_1`, `private_data_c`| > and > |error[E0609]: no field `i` on type `libR_sys::Rcomplex` --> > extendr-api\src\scalar\rcplx_default.rs:105:35 | 105 | > Rcplx(c64::new(val.r, val.i)) | ^ unknown field | = note: available > fields are: `__bindgen_anon_1`, `private_data_c` help: one o...

...; error[E0560]: union `libR_sys::Rcomplex` has no field named `r` > --> extendr-api\src\robj\into_robj.rs:93:20 > | > 93 | Rcomplex { r: 0., i: 0. } > | ^ `libR_sys::Rcomplex` does not have this field > | > = note: available fields are: `__bindgen_anon_1`, `private_data_c` > > and > > error[E0609]: no field `i` on type `libR_sys::Rcomplex` > --> extendr-api\src\scalar\rcplx_default.rs:105:35 > | > 105 | Rcplx(c64::new(val.r, val.i)) > | ^ unknown field > | >...

On 4/3/23 14:07, Michael Milton wrote: > Hi all, > > There seems to have been a breaking change in the R trunk caused by a fix > to bug 18430 <https://bugs.r-project.org/show_bug.cgi?id=18430> that > relates to the layout of the Rcomplex typedef. Previously it was a struct, > but now it's a union by default >

...ler errors such as: >> |error[E0560]: union `libR_sys::Rcomplex` has no field named `r` >> --> extendr-api\src\robj\into_robj.rs:93:20 | 93 | Rcomplex { r: >> 0., i: 0. } | ^ `libR_sys::Rcomplex` does not have this field | = >> note: available fields are: `__bindgen_anon_1`, `private_data_c`| >> and >> |error[E0609]: no field `i` on type `libR_sys::Rcomplex` --> >> extendr-api\src\scalar\rcplx_default.rs:105:35 | 105 | >> Rcplx(c64::new(val.r, val.i)) | ^ unknown field | = note: >> available fields are: `__bindgen_...

I don't think an auto-generated name (along the lines of u or u2) for the anonymous structs would be helpful here. You can see that bindgen is already generating a placeholder name ("__bindgen_anon_1"). A meaningful name might be nice instead, but I get the impression that isn't an option here since that would break the C API. Can I ask, would it make sense for us to hard code in R_LEGACY_RCOMPLEX so that Rust can just ignore the union? Because as I understand the only compiler that a...

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