Prefixed name doesn't work for peer macros

[ssly (Fangchang)]

[Update] Restrictions on Arbitrary Names at Global Scope in SE-0389 and SE-0397

Hi folks, After the acceptance of SE-0389 and SE-0397, further implementation work showed that allowing macros to introduce arbitrary names at global scope is fundamentally prone to creating cycles during type resolution. When performing unqualified name lookup, the compiler must expand all macros that produce arbitrary names, but such a macro may also have arguments that must be type-checked prior to expansion, and doing so would require expanding the very same macro. This limitation is not a…

@attached(peer, names: prefixed(Daedalus))

I don't understand why this doesn't work

[Pippin (Ethan Pippin)]

I don't know if it's a bug if attached to an extension declaration, but your macro should work when attached to the original struct/class/actor declaration.

[sisoje (Lazar Otasevic)]

For me also, prefixed/suffixed does not work for macro generated protocol declarations.
Is it a bug?

[migalc (Miguel Alcântara)]

I'm running into this issue as well. I am working with a Protocol and want to apply a Macro to its extension and I'm having the same error. However, if I attach it to the Protocol then it does compile and execute the macro code.

I don't know how if it's a bug or just not allowed, but it makes sense to me that it should be allowed to do this.

[cprince-foreflight (Christopher Prince)]

I'm also running into this issue. In my case when trying to generate a struct with a specific suffix on the struct name.