`assertMacroExpansion` passes 0 protocols to `ExtensionMacro`. about swift-syntax HOT 4 CLOSED

Synced to Apple’s issue tracker as rdar://131441049

from swift-syntax.

Hey there!

Thanks for bringing this up.

There's a bit of a mismatch between what your test is doing and how the macro actually behaves in real code–since the unit tests expansion is based on a totally different expansion system than source code (compiler) expansion.

If you want to cover conformances in your unit tests, you have to provide a list of conformances to the assertMacroExpansion function. The function has an argument called macroSpecs that you need to fill up if you want to receive conformances in your macro implementation from unit tests.

Here's the documentation for this argument:

Basically, there's this MacroSpec struct with a conformances property that you need to fill in for your tests. It's a new thing that came with swift-syntax version 6.0, which is part of the upcoming Swift 6.0 release. If you're really keen, you can check it out on the main branch right now.

from swift-syntax.

Thanks @Matejkob However I'm on a client's project where we have to support iOS16 and Swift 5. Is there any way to address this without Swift 6?

from swift-syntax.

Ok, I updated to use the main branch and now I can interrogate the protocols.

from swift-syntax.