Macro Adoption Concerns around SwiftSyntax

[dafurman (David Furman)]

@jgoodrick

While we wait for a solution (or maybe new instruction?) from Apple, does anyone happen to know of any stopgap solutions that could be done to reduce the iterative build times when issues pop up in Xcode that are usually solved with a clean+build?

I found success in relying on an XCFramework version of Swift-Syntax for my project using macros. This brought a 15 second compilation increase from the dependency down to around 300 ms for me.
Of course, if you have other dependencies that rely on SwiftSyntax, you'll need to depend on your own forks of those that point to this XCFramework version instead,
Personally for now, I don't depend on too many libraries that use macros, so this is a worthwhile trade of pain, but of course as more libraries adopt macros the overhead of this will increase.