You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Eventough the docs imply that calling the assoicated new function of a generate_pod! type would create a POD rust type that is not the case and the only way to aquire one is to use the rust style initializer {a: x, b: y, ...}.
This is quite problematic because if a C++ field is private that makes Rust-POD construction impossible.
Also I noticed that overloading the constructor is still considered POD to autocxx and I am now unsure if that is actually intended or an oversight.
It should also be noted that the C++ pod monomorphizations get recognized as non-pod:
Description
Eventough the docs imply that calling the assoicated new function of a generate_pod! type would create a POD rust type that is not the case and the only way to aquire one is to use the rust style initializer {a: x, b: y, ...}.
This is quite problematic because if a C++ field is private that makes Rust-POD construction impossible.
Also I noticed that overloading the constructor is still considered POD to autocxx and I am now unsure if that is actually intended or an oversight.
It should also be noted that the C++ pod monomorphizations get recognized as non-pod:
Expected behavior
New calls the constructor of C++ and returns a Rust-POD object.
Additional context
I am writing a thesis on Rust C++ binding generation.
The text was updated successfully, but these errors were encountered: