Assert more with multiple trailing closures (#3)

* Assert more with multiple trailing closures

* Update Deprecations.swift

* fix

* bump

* wip

Author: stephencelis

Package.resolved

@@ -5,8 +5,8 @@
       "kind" : "remoteSourceControl",
       "location" : "https://github.com/pointfreeco/swift-snapshot-testing",
       "state" : {
-        "revision" : "696b86a6d151578bca7c1a2a3ed419a5f834d40f",
-        "version" : "1.13.0"
+        "revision" : "506b6052384d8e97a4bb16fe8680325351c23c64",
+        "version" : "1.14.0"
       }
     },
     {

Package.swift

@@ -18,7 +18,7 @@ let package = Package(
   ],
   dependencies: [
     .package(url: "https://github.com/apple/swift-syntax.git", from: "509.0.0"),
-    .package(url: "https://github.com/pointfreeco/swift-snapshot-testing", from: "1.13.0"),
+    .package(url: "https://github.com/pointfreeco/swift-snapshot-testing", from: "1.14.0"),
   ],
   targets: [
     .target(

README.md

@@ -58,7 +58,7 @@ func testStringify() {
     """
     #stringify(a + b)
     """
-  } matches: {
+  } expansion: {
     """
     (a + b, "a + b")
     """
@@ -86,14 +86,14 @@ assertMacro(["stringify": StringifyMacro.self], record: true) {
   """
   #stringify(a + b)
   """
-} matches: {
+} expansion: {
   """
   (a + b, "a + b")
   """
 }
 ```
 
-Now when you run the test again the freshest expanded macro will be written to the `matches` 
+Now when you run the test again the freshest expanded macro will be written to the `expansion` 
 trailing closure.
 
 If you're writing many tests for a macro, you can avoid the repetitive work of specifying the macros
@@ -115,7 +115,7 @@ class StringifyMacroTests: XCTestCase {
       """
       #stringify(a + b)
       """
-    } matches: {
+    } expansion: {
       """
       (a + b, "a + b")
       """
@@ -142,27 +142,47 @@ override func invokeTest() {
 Macro Testing can also test diagnostics, such as warnings, errors, notes, and fix-its. When a macro
 expansion emits a diagnostic, it will render inline in the test. For example, a macro that adds
 completion handler functions to async functions may emit an error and fix-it when it is applied to a
-non-async function. The resulting macro test will fully capture this information:
+non-async function. The resulting macro test will fully capture this information, including where
+the diagnostics are emitted, how the fix-its are applied, and how the final macro expands:
 
 ```swift
 func testNonAsyncFunctionDiagnostic() {
   assertMacro {
     """
     @AddCompletionHandler
-    func f(a: Int, for b: String, _ value: Double) -> String {
+    func f(a: Int, for b: String) -> String {
       return b
-    }    
+    }
     """
-  } matches: {
+  } diagnostics: {
     """
     @AddCompletionHandler
-    func f(a: Int, for b: String, _ value: Double) -> String {
+    func f(a: Int, for b: String) -> String {
     ┬───
     ╰─ 🛑 can only add a completion-handler variant to an 'async' function
        ✏️ add 'async'
       return b
     }
     """
+  } fixes: {
+    """
+    @AddCompletionHandler
+    func f(a: Int, for b: String) async -> String {
+      return b
+    }
+    """
+  } expansion: {
+    """
+    func f(a: Int, for b: String) async -> String {
+      return b
+    }
+
+    func f(a: Int, for b: String, completionHandler: @escaping (String) -> Void) {
+      Task {
+        completionHandler(await f(a: a, for: b, value))
+      }
+    }
+    """
   }
 }
 ```