ReactiveCocoa
diff --git a/‎Examples/CaseStudies/SwiftUICaseStudies/01-GettingStarted-FocusState.swift
Lines changed: 0 additions & 1 deletion b/‎Examples/CaseStudies/SwiftUICaseStudies/01-GettingStarted-FocusState.swift
Lines changed: 0 additions & 1 deletion
diff --git a/‎Package.resolved
Lines changed: 2 additions & 2 deletions b/‎Package.resolved
Lines changed: 2 additions & 2 deletions
diff --git a/‎Sources/ComposableArchitecture/Documentation.docc/ComposableArchitecture.md
Lines changed: 1 addition & 1 deletion b/‎Sources/ComposableArchitecture/Documentation.docc/ComposableArchitecture.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎Sources/ComposableArchitecture/Documentation.docc/Extensions/Deprecations/SwiftUIDeprecations.md
Lines changed: 0 additions & 4 deletions b/‎Sources/ComposableArchitecture/Documentation.docc/Extensions/Deprecations/SwiftUIDeprecations.md
Lines changed: 0 additions & 4 deletions
diff --git a/‎Sources/ComposableArchitecture/Documentation.docc/Extensions/Effect.md
Lines changed: 13 additions & 13 deletions b/‎Sources/ComposableArchitecture/Documentation.docc/Extensions/Effect.md
Lines changed: 13 additions & 13 deletions
diff --git a/‎Sources/ComposableArchitecture/Documentation.docc/Extensions/TestStore.md
Lines changed: 2 additions & 2 deletions b/‎Sources/ComposableArchitecture/Documentation.docc/Extensions/TestStore.md
Lines changed: 2 additions & 2 deletions
diff --git a/‎Sources/ComposableArchitecture/Effect.swift
Lines changed: 85 additions & 84 deletions b/‎Sources/ComposableArchitecture/Effect.swift
Lines changed: 85 additions & 84 deletions
diff --git a/‎Sources/ComposableArchitecture/Effects/ConcurrencySupport.swift
Lines changed: 3 additions & 3 deletions b/‎Sources/ComposableArchitecture/Effects/ConcurrencySupport.swift
Lines changed: 3 additions & 3 deletions
diff --git a/‎Sources/ComposableArchitecture/Internal/Deprecations.swift
Lines changed: 17 additions & 0 deletions b/‎Sources/ComposableArchitecture/Internal/Deprecations.swift
Lines changed: 17 additions & 0 deletions
diff --git a/‎Sources/ComposableArchitecture/SwiftUI/Binding.swift
Lines changed: 5 additions & 7 deletions b/‎Sources/ComposableArchitecture/SwiftUI/Binding.swift
Lines changed: 5 additions & 7 deletions
@@ -57,7 +57,6 @@ struct FocusDemoView: View {
         VStack {
           TextField("Username", text: viewStore.binding(\.$username))
             .focused($focusedField, equals: .username)
-
           SecureField("Password", text: viewStore.binding(\.$password))
             .focused($focusedField, equals: .password)
           Button("Sign In") {
 
@@ -13,7 +13,7 @@
 ### State management
 
 - ``ReducerProtocol``
-- ``EffectProducer``
+- ``EffectTask``
 - ``Store``
 - ``ViewStore``
 
 
@@ -33,9 +33,5 @@ Avoid using deprecated APIs in your app. Select a method to see the replacement
 - ``WithViewStore/Action``
 - ``WithViewStore/State``
 
-### View state
-
-- ``ActionSheetState``
-
 <!--DocC: Can't currently document `View` extensions-->
 <!--### View Modifiers-->
@@ -1,39 +1,39 @@
-# ``ComposableArchitecture/EffectProducer``
+# ``ComposableArchitecture/EffectTask``
 
 ## Topics
 
 ### Creating an effect
 
-- ``none``
-- ``task(priority:operation:catch:file:fileID:line:)``
-- ``run(priority:operation:catch:file:fileID:line:)``
-- ``fireAndForget(priority:_:)``
+- ``EffectProducer/none``
+- ``EffectProducer/task(priority:operation:catch:file:fileID:line:)``
+- ``EffectProducer/run(priority:operation:catch:file:fileID:line:)``
+- ``EffectProducer/fireAndForget(priority:_:)``
 - ``TaskResult``
 
 ### Cancellation
 
-- ``cancellable(id:cancelInFlight:)-29q60``
-- ``cancel(id:)-6hzsl``
-- ``cancel(ids:)-1cqqx``
+- ``EffectProducer/cancellable(id:cancelInFlight:)-29q60``
+- ``EffectProducer/cancel(id:)-6hzsl``
+- ``EffectProducer/cancel(ids:)-1cqqx``
 - ``withTaskCancellation(id:cancelInFlight:operation:)-4dtr6``
 
 ### Composition
 
-- ``map(_:)-yn70``
-- ``merge(_:)-45guh``
-- ``merge(_:)-3d54p``
+- ``EffectProducer/map(_:)-yn70``
+- ``EffectProducer/merge(_:)-45guh``
+- ``EffectProducer/merge(_:)-3d54p``
 
 ### Concurrency
 
 - ``UncheckedSendable``
 
 ### Testing
 
-- ``unimplemented(_:)``
+- ``EffectProducer/unimplemented(_:)``
 
 ### SwiftUI integration
 
-- ``animation(_:)``
+- ``EffectProducer/animation(_:)``
 
 ### Deprecations
 
 
@@ -4,7 +4,7 @@
 
 ### Creating a test store
 
-- ``init(initialState:reducer:file:line:)``
+- ``init(initialState:reducer:prepareDependencies:file:line:)``
 
 ### Configuring a test store
 
@@ -18,7 +18,7 @@
 - ``receive(_:timeout:assert:file:line:)-1rwdd``
 - ``receive(_:timeout:assert:file:line:)-4e4m0``
 - ``receive(_:timeout:assert:file:line:)-3myco``
-- ``finish(timeout:file:line:)``
+- ``finish(timeout:file:line:)-53gi5``
 - ``TestStoreTask``
 
 ### Methods for skipping actions and effects
 
@@ -6,35 +6,55 @@ import XCTestDynamicOverlay
   import SwiftUI
 #endif
 
-/// A type that encapsulates a unit of work that can be run in the outside world, and can feed
-/// actions back to the ``Store``.
-///
-/// Effects are the perfect place to do side effects, such as network requests, saving/loading
-/// from disk, creating timers, interacting with dependencies, and more. They are returned from
-/// reducers so that the ``Store`` can perform the effects after the reducer is done running.
-///
-/// There are 2 distinct ways to create an `Effect`: one using Swift's native concurrency tools, and
-/// the other using ReactiveSwift framework:
-///
-/// * If using Swift's native structured concurrency tools then there are 3 main ways to create an
-/// effect, depending on if you want to emit one single action back into the system, or any number
-/// of actions, or just execute some work without emitting any actions:
-///   * ``EffectProducer/task(priority:operation:catch:file:fileID:line:)``
-///   * ``EffectProducer/run(priority:operation:catch:file:fileID:line:)``
-///   * ``EffectProducer/fireAndForget(priority:_:)``
-/// * If using ReactiveSwift in your application, in particular for the dependencies of your feature
-/// then you can create effects by making use of any of ReactiveSwift's operators, and then erasing the
-/// publisher type to ``EffectProducer`` with either `eraseToEffect` or `catchToEffect`. Note that
-/// the ReactiveSwift interface to ``EffectProducer`` is considered soft deprecated, and you should
-/// eventually port to Swift's native concurrency tools.
-///
-/// > Important: ``Store`` is not thread safe, and so all effects must receive values on the same
-/// thread. This is typically the main thread,  **and** if the store is being used to drive UI then
-/// it must receive values on the main thread.
-/// >
-/// > This is only an issue if using the ReactiveSwift interface of ``EffectProducer`` as mentioned
-/// above. If  you are using Swift's concurrency tools and the `.task`, `.run` and `.fireAndForget`
-/// functions on ``EffectTask``, then threading is automatically handled for you.
+/// This type is deprecated in favor of ``EffectTask``. See its documentation for more information.
+@available(
+  iOS,
+  deprecated: 9999.0,
+  message:
+    """
+    'EffectProducer' has been deprecated in favor of 'EffectTask'.
+
+     You are encouraged to use `EffectTask<Action>` to model the ouput of your reducers, and to use Swift concurrency to model asynchrony in dependencies.
+
+     See the migration roadmap for more information: https://github.com/pointfreeco/swift-composable-architecture/discussions/1477
+    """
+)
+@available(
+  macOS,
+  deprecated: 9999.0,
+  message:
+    """
+    'EffectProducer' has been deprecated in favor of 'EffectTask'.
+
+     You are encouraged to use `EffectTask<Action>` to model the ouput of your reducers, and to use Swift concurrency to model asynchrony in dependencies.
+
+     See the migration roadmap for more information: https://github.com/pointfreeco/swift-composable-architecture/discussions/1477
+    """
+)
+@available(
+  tvOS,
+  deprecated: 9999.0,
+  message:
+    """
+    'EffectProducer' has been deprecated in favor of 'EffectTask'.
+
+     You are encouraged to use `EffectTask<Action>` to model the ouput of your reducers, and to use Swift concurrency to model asynchrony in dependencies.
+
+     See the migration roadmap for more information: https://github.com/pointfreeco/swift-composable-architecture/discussions/1477
+    """
+)
+@available(
+  watchOS,
+  deprecated: 9999.0,
+  message:
+    """
+    'EffectProducer' has been deprecated in favor of 'EffectTask'.
+
+     You are encouraged to use `EffectTask<Action>` to model the ouput of your reducers, and to use Swift concurrency to model asynchrony in dependencies.
+
+     See the migration roadmap for more information: https://github.com/pointfreeco/swift-composable-architecture/discussions/1477
+    """
+)
 public struct EffectProducer<Action, Failure: Error> {
   @usableFromInline
   enum Operation {
@@ -63,20 +83,38 @@ extension EffectProducer {
   }
 }
 
-/// A convenience type alias for referring to an effect that can never fail, like the kind of
-/// ``EffectProducer`` returned by a reducer after processing an action.
+/// A type that encapsulates a unit of work that can be run in the outside world, and can feed
+/// actions back to the ``Store``.
 ///
-/// Instead of specifying `Never` as `Failure`:
+/// Effects are the perfect place to do side effects, such as network requests, saving/loading
+/// from disk, creating timers, interacting with dependencies, and more. They are returned from
+/// reducers so that the ``Store`` can perform the effects after the reducer is done running.
 ///
-/// ```swift
-/// func reduce(into state: inout State, action: Action) -> EffectProducer<Action, Never> { … }
-/// ```
+/// There are 2 distinct ways to create an `Effect`: one using Swift's native concurrency tools, and
+/// the other using Apple's Combine framework:
 ///
-/// You can specify a single generic:
+/// * If using Swift's native structured concurrency tools then there are 3 main ways to create an
+/// effect, depending on if you want to emit one single action back into the system, or any number
+/// of actions, or just execute some work without emitting any actions:
+///   * ``EffectProducer/task(priority:operation:catch:file:fileID:line:)``
+///   * ``EffectProducer/run(priority:operation:catch:file:fileID:line:)``
+///   * ``EffectProducer/fireAndForget(priority:_:)``
+/// * If using Combine in your application, in particular for the dependencies of your feature
+/// then you can create effects by making use of any of Combine's operators, and then erasing the
+/// publisher type to ``EffectProducer`` with either `eraseToEffect` or `catchToEffect`. Note that
+/// the Combine interface to ``EffectProducer`` is considered soft deprecated, and you should
+/// eventually port to Swift's native concurrency tools.
 ///
-/// ```swift
-/// func reduce(into state: inout State, action: Action) -> EffectTask<Action>  { … }
-/// ```
+/// > Important: The publisher interface to ``EffectTask`` is considered deperecated, and you should
+/// try converting any uses of that interface to Swift's native concurrency tools.
+/// >
+/// > Also, ``Store`` is not thread safe, and so all effects must receive values on the same
+/// thread. This is typically the main thread,  **and** if the store is being used to drive UI then
+/// it must receive values on the main thread.
+/// >
+/// > This is only an issue if using the Combine interface of ``EffectProducer`` as mentioned
+/// above. If  you are using Swift's concurrency tools and the `.task`, `.run` and `.fireAndForget`
+/// functions on ``EffectTask``, then threading is automatically handled for you.
 public typealias EffectTask<Action> = Effect<Action, Never>
 
 extension EffectProducer where Failure == Never {
@@ -614,57 +652,20 @@ extension EffectProducer {
 }
 
 @available(
-  iOS,
-  deprecated: 9999.0,
+  *,
   message:
     """
-    'Effect' has been deprecated in favor of 'EffectTask' when `Failure == Never`, or
-    `EffectProducer<Output, Failure>` in general.
+    'Effect' has been deprecated in favor of 'EffectTask' when 'Failure == Never', or 'EffectProducer<Output, Failure>' in general.
     
-    You are encouraged to use `EffectTask<Action>` to model the ouput of your reducers, and to Swift
-    concurrency to model failable streams of values.
+    You are encouraged to use 'EffectTask<Action>' to model the output of your reducers, and to use Swift concurrency to model failable streams of values.
 
-    See the migration roadmap for more information: https://github.com/pointfreeco/swift-composable-architecture/discussions/1477
-    """
-)
-@available(
-  macOS,
-  deprecated: 9999.0,
-  message:
-    """
-    'Effect' has been deprecated in favor of 'EffectTask' when `Failure == Never`, or
-    `EffectProducer<Output, Failure>` in general.
-    
-    You are encouraged to use `EffectTask<Action>` to model the ouput of your reducers, and to Swift
-    concurrency to model failable streams of values.
+    To find and replace instances of 'Effect<Action, Never>' to 'EffectTask<Action, Never>' in your codebase, use the following regular expression:
 
-    See the migration roadmap for more information: https://github.com/pointfreeco/swift-composable-architecture/discussions/1477
-    """
-)
-@available(
-  tvOS,
-  deprecated: 9999.0,
-  message:
-    """
-    'Effect' has been deprecated in favor of 'EffectTask' when `Failure == Never`, or
-    `EffectProducer<Output, Failure>` in general.
-    
-    You are encouraged to use `EffectTask<Action>` to model the ouput of your reducers, and to Swift
-    concurrency to model failable streams of values.
+      Find:
+        Effect<([^,]+), Never>
 
-    See the migration roadmap for more information: https://github.com/pointfreeco/swift-composable-architecture/discussions/1477
-    """
-)
-@available(
-  watchOS,
-  deprecated: 9999.0,
-  message:
-    """
-    'Effect' has been deprecated in favor of 'EffectTask' when `Failure == Never`, or
-    `EffectProducer<Output, Failure>` in general.
-    
-    You are encouraged to use `EffectTask<Action>` to model the ouput of your reducers, and to Swift
-    concurrency to model failable streams of values.
+      Replace:
+        EffectTask<$1>
 
     See the migration roadmap for more information: https://github.com/pointfreeco/swift-composable-architecture/discussions/1477
     """
 
@@ -326,11 +326,11 @@
     /// - Parameters: operation: An operation to be performed on the actor with the underlying value.
     /// - Returns: The result of the operation.
     public func withValue<T: Sendable>(
-      _ operation: @Sendable (inout Value) async throws -> T
-    ) async rethrows -> T {
+      _ operation: @Sendable (inout Value) throws -> T
+    ) rethrows -> T {
       var value = self.value
       defer { self.value = value }
-      return try await operation(&value)
+      return try operation(&value)
     }
 
     /// Overwrite the isolated value with a new value.
 
@@ -10,6 +10,23 @@ import XCTestDynamicOverlay
   import os
 #endif
 
+// MARK: - Deprecated after 0.47.2
+
+extension ActorIsolated {
+  @available(
+    *,
+    deprecated,
+    message: "Use the non-async version of 'withValue'."
+  )
+  public func withValue<T: Sendable>(
+    _ operation: @Sendable (inout Value) async throws -> T
+  ) async rethrows -> T {
+    var value = self.value
+    defer { self.value = value }
+    return try await operation(&value)
+  }
+}
+
 // MARK: - Deprecated after 0.45.0:
 
 #if canImport(SwiftUI)
 
@@ -82,12 +82,11 @@ extension BindableState: CustomReflectable {
   }
 }
 
-// Until we can use swift-custom-dump this has to be commented out
-//  extension BindableState: CustomDumpRepresentable {
-//    public var customDumpValue: Any {
-//      self.wrappedValue
-//    }
-//  }
+extension BindableState: CustomDumpRepresentable {
+  public var customDumpValue: Any {
+    self.wrappedValue
+  }
+}
 
 extension BindableState: CustomDebugStringConvertible where Value: CustomDebugStringConvertible {
   public var debugDescription: String {
@@ -157,7 +156,6 @@ extension BindableAction {
       )
     }
   }
-
 #endif
 
 /// An action that describes simple mutations to some root state at a writable key path.
Original file line number	Diff line number	Diff line change
`@@ -82,12 +82,11 @@ extension BindableState: CustomReflectable {`
`82`	`82`	`}`
`83`	`83`	`}`
`84`	`84`
`85`		`-// Until we can use swift-custom-dump this has to be commented out`
`86`		`-// extension BindableState: CustomDumpRepresentable {`
`87`		`-// public var customDumpValue: Any {`
`88`		`-// self.wrappedValue`
`89`		`-// }`
`90`		`-// }`
	`85`	`+extension BindableState: CustomDumpRepresentable {`
	`86`	`+ public var customDumpValue: Any {`
	`87`	`+ self.wrappedValue`
	`88`	`+ }`
	`89`	`+}`
`91`	`90`
`92`	`91`	`extension BindableState: CustomDebugStringConvertible where Value: CustomDebugStringConvertible {`
`93`	`92`	`public var debugDescription: String {`
`@@ -157,7 +156,6 @@ extension BindableAction {`
`157`	`156`	`)`
`158`	`157`	`}`
`159`	`158`	`}`
`160`		`-`
`161`	`159`	`#endif`
`162`	`160`
`163`	`161`	`/// An action that describes simple mutations to some root state at a writable key path.`