Tags: sketchar/Swinject
Tags
fix: remove @mainactor argument overloads that break resolve type mat… …ching
feat: add @mainactor factory closure overloads Add @MainActor-isolated register() and initCompleted() overloads for Swift 6 strict concurrency support. These allow registering services with closures that create @MainActor-isolated types without requiring MainActor.assumeIsolated workarounds in user code. The @mainactor closures are erased via MainActor.assumeIsolated wrapper at storage time, so the existing resolve path works unchanged.
feat: add @mainactor factory closure overloads Add @MainActor-isolated register() and initCompleted() overloads for Swift 6 strict concurrency support. These allow registering services with closures that create @MainActor-isolated types without requiring MainActor.assumeIsolated workarounds in user code. The @mainactor closures are erased via MainActor.assumeIsolated wrapper at storage time, so the existing resolve path works unchanged.
feat: add @mainactor factory closure overloads Add @MainActor-isolated register() and initCompleted() overloads for Swift 6 strict concurrency support. These allow registering services with closures that create @MainActor-isolated types without requiring MainActor.assumeIsolated workarounds in user code. The @mainactor closures are erased via MainActor.assumeIsolated wrapper at storage time, so the existing resolve path works unchanged.
feat: add @mainactor factory closure overloads Add @MainActor-isolated register() and initCompleted() overloads for Swift 6 strict concurrency support. These allow registering services with closures that create @MainActor-isolated types without requiring MainActor.assumeIsolated workarounds in user code. The @mainactor closures are erased via MainActor.assumeIsolated wrapper at storage time, so the existing resolve path works unchanged.
PreviousNext