Fixing macros that expand to include other macros

I was experimenting with creating my own peer macro that expands to include @Test and ran into some compiler bugs, so I was motivated to fix them. However, fixing the bugs includes some subtle user-facing changes, so I wanted to gauge other folks' opinions about whether this is just a bug fix or something that we need to be more deliberate about. The problem is this: let's say I have a peer macro called @MyTest: @MyTest func global() {} struct S { @MyTest func member() {} } and this is mea...