tree 01094a66623ed15e14c9b4b58d111c743cfbd68d
parent d6f3e2ad69e19b47985a273214c31dfa72ac8f5c
author Devin Jeanpierre <jeanpierreda@google.com> 1658753529 -0700
committer Copybara-Service <copybara-worker@google.com> 1658753571 -0700

Allow either order of `derive(CtorFrom_Default)` / `#[recursively_pinned]`.

Primary error: the layout of `CtorInitializedFields` is ignored, I can just clear the attrs! Oopsie woopsie.

However, even if we do that, there's other problems that make these macros compose very poorly in the original order. Apparently, ideally, either order should work, but this is definitely messy to support.

Another solution would be to detect if they're misordered and swap the order in the macro.

I think this is worth deferring to some later time to do "properly" -- this only matters during the process of porting a C++ class to Rust, and that's somewhat of a theoretical concern given the current state of interop.

PiperOrigin-RevId: 463065300