You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Sources/DistributedActors/ActorAddress.swift
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,7 @@ extension ClusterSystem {
56
56
///
57
57
/// Storing an `ActorID` instead of the concrete `DistributedActor` is also a common pattern to avoid
58
58
/// retaining the actor, while retaining the ability to know if we have already stored this actor or not.
59
-
/// For example, in a lobby system, we might need to only store actor identifiers, and ``LifecycleWatch/watchTermination``
59
+
/// For example, in a lobby system, we might need to only store actor identifiers, and ``LifecycleWatch/watchTermination(of:whenTerminated:file:line:)``
60
60
/// some actors, in order to not retain them in the lobby actor itself. If the same actor messages us again to "join",
61
61
/// we would already know that we have already seen it, and could handle it joining again in some other way.
/// A leader is a specific `Member` which was selected to fulfil the leadership role for the time being.
177
-
/// A leader returning a non-nil value, guarantees that the same Member existing as part of this `Membership` as well (non-members cannot be leaders).
178
+
/// A leader is a specific ``Cluster/Member`` which was selected to fulfil the leadership role for the time being.
179
+
///
180
+
/// A leader returning a non-nil value, guarantees that the same ``Cluster/Member`` existing as part of this ``Cluster/Membership`` as well (non-members cannot be leaders).
178
181
///
179
182
/// Clustering offered by this project does not really designate any "special" nodes; yet sometimes a leader may be useful to make decisions more efficient or centralized.
180
183
/// Leaders may be selected using various strategies, the most simple one being sorting members by their addresses and picking the "lowest".
0 commit comments