Fix deprecated message cannot handle in swift 5 (#51)

Co-authored-by: Konrad `ktoso` Malawski <[email protected]>

Author: sidepelican

Sources/ServiceContextModule/ServiceContext.swift

@@ -260,14 +260,12 @@ extension ServiceContext {
     }
 
     @available(*, deprecated, message: "Use the method with the isolation parameter instead.")
+    // Deprecated trick to avoid executor hop here; 6.0 introduces the proper replacement: #isolation
     @_disfavoredOverload
     public static func withValue<T>(_ value: ServiceContext?, operation: () async throws -> T) async rethrows -> T {
         try await ServiceContext.$current.withValue(value, operation: operation)
     }
     #else
-    // Deprecated trick to avoid executor hop here; 6.0 introduces the proper replacement: #isolation
-    @available(*, deprecated, message: "Prefer withValue(_:isolation:operation:)")
-    @_disfavoredOverload
     @_unsafeInheritExecutor
     public static func withValue<T>(_ value: ServiceContext?, operation: () async throws -> T) async rethrows -> T {
         try await ServiceContext.$current.withValue(value, operation: operation)

Tests/ServiceContextTests/ServiceContextTests.swift

@@ -94,6 +94,9 @@ final class ServiceContextTests: XCTestCase {
             ServiceContext.withValue(.topLevel) {
                 value = 12  // should produce no warnings
             }
+            await ServiceContext.withValue(.topLevel) { () async in
+                value = 12  // should produce no warnings
+            }
         }
     }