Run swift-format

(cherry picked from commit ef137808e73b430db71a77c8407fd4c3b71a7372)

Author: mbrandonw

Sources/ComposableArchitecture/SwiftUI/Binding.swift

@@ -142,7 +142,8 @@ extension ViewStore where ViewAction: BindableAction, ViewAction.State == ViewSt
       send: { value in
         #if DEBUG
           let debugger = BindableActionViewStoreDebugger(
-            value: value, bindableActionType: ViewAction.self, file: file, fileID: fileID, line: line
+            value: value, bindableActionType: ViewAction.self, file: file, fileID: fileID,
+            line: line
           )
           let set: (inout ViewState) -> Void = {
             $0[keyPath: keyPath].wrappedValue = value

Sources/ComposableArchitecture/ViewStore.swift

@@ -160,7 +160,8 @@ public final class ViewStore<ViewState, ViewAction> {
   @available(
     iOS,
     deprecated: 9999.0,
-    message: """
+    message:
+      """
       Use 'init(_:observe:removeDuplicates:)' to make state observation explicit.
 
       When using ViewStore you should take care to observe only the pieces of state that your view needs to do its job, especially towards the root of the application. See the performance article for more details:
@@ -171,7 +172,8 @@ public final class ViewStore<ViewState, ViewAction> {
   @available(
     macOS,
     deprecated: 9999.0,
-    message: """
+    message:
+      """
       Use 'init(_:observe:removeDuplicates:)' to make state observation explicit.
 
       When using ViewStore you should take care to observe only the pieces of state that your view needs to do its job, especially towards the root of the application. See the performance article for more details:
@@ -182,7 +184,8 @@ public final class ViewStore<ViewState, ViewAction> {
   @available(
     tvOS,
     deprecated: 9999.0,
-    message: """
+    message:
+      """
       Use 'init(_:observe:removeDuplicates:)' to make state observation explicit.
 
       When using ViewStore you should take care to observe only the pieces of state that your view needs to do its job, especially towards the root of the application. See the performance article for more details:
@@ -193,7 +196,8 @@ public final class ViewStore<ViewState, ViewAction> {
   @available(
     watchOS,
     deprecated: 9999.0,
-    message: """
+    message:
+      """
       Use 'init(_:observe:removeDuplicates:)' to make state observation explicit.
 
       When using ViewStore you should take care to observe only the pieces of state that your view needs to do its job, especially towards the root of the application. See the performance article for more details:
@@ -626,7 +630,8 @@ extension ViewStore where ViewState: Equatable {
   @available(
     iOS,
     deprecated: 9999.0,
-    message: """
+    message:
+      """
       Use 'init(_:observe:)' to make state observation explicit.
 
       When using ViewStore you should take care to observe only the pieces of state that your view needs to do its job, especially towards the root of the application. See the performance article for more details:
@@ -637,7 +642,8 @@ extension ViewStore where ViewState: Equatable {
   @available(
     macOS,
     deprecated: 9999.0,
-    message: """
+    message:
+      """
       Use 'init(_:observe:)' to make state observation explicit.
 
       When using ViewStore you should take care to observe only the pieces of state that your view needs to do its job, especially towards the root of the application. See the performance article for more details:
@@ -648,7 +654,8 @@ extension ViewStore where ViewState: Equatable {
   @available(
     tvOS,
     deprecated: 9999.0,
-    message: """
+    message:
+      """
       Use 'init(_:observe:)' to make state observation explicit.
 
       When using ViewStore you should take care to observe only the pieces of state that your view needs to do its job, especially towards the root of the application. See the performance article for more details:
@@ -659,7 +666,8 @@ extension ViewStore where ViewState: Equatable {
   @available(
     watchOS,
     deprecated: 9999.0,
-    message: """
+    message:
+      """
       Use 'init(_:observe:)' to make state observation explicit.
 
       When using ViewStore you should take care to observe only the pieces of state that your view needs to do its job, especially towards the root of the application. See the performance article for more details: