Run swift-format

Sources/ComposableArchitecture/TestStore.swift

@@ -1008,7 +1008,7 @@ extension TestStore where State: Equatable {
   /// <doc:Testing#Non-exhaustive-testing>), which allow you to assert on a subset of the things
   /// happening inside your features. For example, you can send an action in a child feature
   /// without asserting on how many changes in the system, and then tell the test store to
-  /// ``finish(timeout:fileID:file:line:column:)-klnc`` by executing all of its effects, and finally 
+  /// ``finish(timeout:fileID:file:line:column:)-klnc`` by executing all of its effects, and finally
   /// to ``skipReceivedActions(strict:fileID:file:line:column:)`` to receive all actions. After that
   /// is done you can assert on the final state of the store:
   ///

Sources/ComposableArchitecture/UIKit/NavigationStackControllerUIKit.swift

@@ -68,4 +68,3 @@
     }
   }
 #endif
-

Tests/ComposableArchitectureTests/RuntimeWarningTests.swift

@@ -249,7 +249,7 @@
         ] = .init()
       } issueMatcher: {
         $0.compactDescription == """
-          failed - A navigation stack binding at "file.swift:1" was written to with a path that \ 
+          failed - A navigation stack binding at "file.swift:1" was written to with a path that \
           has the same number of elements that already exist in the store. A view should only \
           write to this binding with a path that has pushed a new element onto the stack, or \
           popped one or more elements from the stack.