I feel like that discussion settled on it being correct to disable synthesis of the memberwise init when a macro creates an init" (because it follows the rules as-if you'd written the code without the macro), but that we might consider some kind of @doesNotSuppressMemberwiseInit attribute separately.
Interesting. If we can't model this directly, it means using arbitrary for such names, which is a pessimization for compile times, but shouldn't affect what a macro can do. I'm ambivalent about this, other than wanting a name more descriptive than modified if we do it.
Doug