|
5 | 5 |
|
6 | 6 | ## Swift 6.0
|
7 | 7 |
|
| 8 | +* [SE-0428][]: |
| 9 | + Distributed actors now have the ability to support complete split server / |
| 10 | + client systems, thanks to the new `@Resolvable` macro and runtime changes. |
| 11 | + |
| 12 | + It is now possible to share an "API module" between a client and server |
| 13 | + application, declare a resolvable distributed actor protocol with the expected |
| 14 | + API contract and perform calls on it, without knowing the specific type the |
| 15 | + server is implementing those actors as. |
| 16 | + |
| 17 | + Declaring such protocol looks like this: |
| 18 | + |
| 19 | +```swift |
| 20 | +import Distributed |
| 21 | + |
| 22 | +@Resolvable |
| 23 | +protocol Greeter where ActorSystem: DistributedActorSystem<any Codable> { |
| 24 | + distributed func greet(name: String) -> String |
| 25 | +} |
| 26 | +``` |
| 27 | + |
| 28 | +And the module structure to support such applications looks like this: |
| 29 | + |
| 30 | +``` |
| 31 | + ┌────────────────────────────────────────┐ |
| 32 | + │ API Module │ |
| 33 | + │========================================│ |
| 34 | + │ @Resolvable │ |
| 35 | + │ protocol Greeter: DistributedActor { │ |
| 36 | + ┌───────┤ distributed func greet(name: String) ├───────┐ |
| 37 | + │ │ } │ │ |
| 38 | + │ └────────────────────────────────────────┘ │ |
| 39 | + │ │ |
| 40 | + ▼ ▼ |
| 41 | +┌────────────────────────────────────────────────┐ ┌──────────────────────────────────────────────┐ |
| 42 | +│ Client Module │ │ Server Module │ |
| 43 | +│================================================│ │==============================================│ |
| 44 | +│ let g = try $Greeter.resolve(...) /*new*/ │ │ distributed actor EnglishGreeter: Greeter { │ |
| 45 | +│ try await greeter.hello(name: ...) │ │ distributed func greet(name: String) { │ |
| 46 | +└────────────────────────────────────────────────┘ │ "Greeting in english, for \(name)!" │ |
| 47 | +/* Client cannot know about EnglishGreeter type */ │ } │ |
| 48 | + │ } │ |
| 49 | + └──────────────────────────────────────────────┘ |
| 50 | +``` |
| 51 | + |
| 52 | +* [SE-0424][]: |
| 53 | + Serial executor gain a new customization point `checkIsolation()`, which can be |
| 54 | + implemented by custom executor implementations in order to provide a last resort |
| 55 | + check before the isolation asserting APIs such as `Actor.assumeIsolated` or |
| 56 | + `assertIsolated` fail and crash. |
| 57 | + |
| 58 | + This specifically enables Dispatch to implement more sophisticated isolation |
| 59 | + checking, and now even an actor which is "on a queue which is targeting |
| 60 | + another specific queue" can be properly detected using these APIs. |
| 61 | + |
8 | 62 | * [SE-0430][]:
|
9 | 63 |
|
10 | 64 | Region Based Isolation is now extended to enable the application of an
|
@@ -10332,6 +10386,8 @@ using the `.dynamicType` member to retrieve the type of an expression should mig
|
10332 | 10386 | [SE-0422]: https://github.com/apple/swift-evolution/blob/main/proposals/0422-caller-side-default-argument-macro-expression.md
|
10333 | 10387 | [SE-0427]: https://github.com/apple/swift-evolution/blob/main/proposals/0427-noncopyable-generics.md
|
10334 | 10388 | [SE-0414]: https://github.com/apple/swift-evolution/blob/main/proposals/0414-region-based-isolation.md
|
| 10389 | +[SE-0424]: https://github.com/apple/swift-evolution/blob/main/proposals/0424-custom-isolation-checking-for-serialexecutor.md |
| 10390 | +[SE-0428]: https://github.com/apple/swift-evolution/blob/main/proposals/0428-resolve-distributed-actor-protocols.md |
10335 | 10391 | [SE-0430]: https://github.com/apple/swift-evolution/blob/main/proposals/0430-transferring-parameters-and-results.md
|
10336 | 10392 | [#64927]: <https://github.com/apple/swift/issues/64927>
|
10337 | 10393 | [#42697]: <https://github.com/apple/swift/issues/42697>
|
|
0 commit comments