Relaxing restrictions on macros producing extension declarations

Could we mitigate the eager expansion issue by letting extension macros specify what types they're going to extend? For example, @JetForMe wants to write a macro that always extends the same two types, FocusCommandValues and View. It seems like it should be possible to optimize using that knowledge.

1 Like