Macros seem to be expanded in their own sub-scope

[tmcdonell]

Macros seem to be expanded in their own sub-scope

[tmcdonell]

Correction, it seems like using a freestanding declaration method never worked either. I just tested the example from #72307 and that also executes the defer statement immediately (swift-5.9-release). Same as if I change this example to a declaration macro.

@i2h3 if I just add some print statements to your example I get the following:

> swift run
Building for debugging...
[8/8] Linking SignpostClient
Build complete! (1.49s)
Signpost begin: sayHello()
Signpost defer: sayHello()
Hello!

Did you also encounter this behaviour (in your larger application)?

Edit: For completeness, here is the diff:

diff --git a/Sources/SignpostMacros/SignpostMacro.swift b/Sources/SignpostMacros/SignpostMacro.swift
index c5fb8a8..b9a3677 100644
--- a/Sources/SignpostMacros/SignpostMacro.swift
+++ b/Sources/SignpostMacros/SignpostMacro.swift
@@ -10,9 +10,11 @@ public struct SignpostMacro: DeclarationMacro {
                 stringLiteral: """
                 let signpostID = signposter.makeSignpostID()
                 let signpostIntervalState = signposter.beginInterval(#function, id: signpostID)
+                print("Signpost begin: \\(#function)")
 
                 defer {
                     signposter.endInterval(#function, signpostIntervalState)
+                    print("Signpost defer: \\(#function)")
                 }
                 """
             ),

[tmcdonell]

According to the description of how macros are expanded, it seems that point (3) is not accurate; the compiler does not replace the macro call with its expanded form, rather it puts the expansion in a sub-tree and replaces the call with that. The diagram above this list also seems to imply the expansion should happen inline, but that doesn't appear to be the behaviour I am observing. Or, am I just doing something wrong? Any advice?