1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
//! This module provides the building blocks for creating an actor able to process dynamically
//! typed requests, while maintaing type-safety and returning the appropriately typed responses.
//!
//! # Rationale
//!
//! In the actor model, an actor is a long lived components that communicates with other services
//! by sharing messages. Those messages are usually typed, meaning an actor know upront which type
//! of requests they will receive. While this covers the majority of use-cases, there might be some
//! where this is not applicable, and workarounds result in inconvenient solutions compared to
//! paying a little cost of a virtual table lookup for dynamic dispatching.
//!
//! A class of such examples is one where an actor is tied to some non-cheapy-clonable resources. In this
//! case, it is not possible to provide multiple actors for each type of message we want to
//! communicate in our application by assumption.
//! A member of such class, that motivated this code from first principles, is an actor backed by a
//! OS thread that runs in a isolated Linux network namespace. This primitive allows to interact
//! with many Linux namespace within the same binary, which is the raison d'etre of this create.
//! Trying to clone this actor for each message type means spwaning another OS thread and, in case
//! there is necessity of asynchronous code within the actor logic, an additional asynchronous
//! runtime.
//!
//! # Cast Abstraction
//!
//! The channel is generic over a [`Cast`] strategy that determines how values are type-erased
//! and recovered. This abstraction enables different communication scenarios:
//!
//! - [`AnyCast`]: In-process communication using `dyn Any` (default, zero serialization overhead)
//! - Future implementations could support cross-process communication via serialization
use ;
use ;
/// Trait for type erasure and reconstruction strategies.
///
/// This trait abstracts the mechanism used to erase and recover types when sending
/// messages through the dynamic channel. Different implementations enable different
/// communication scenarios.
///
/// # Safety Contract
///
/// Implementations must guarantee that `recover::<T>` correctly reconstructs a value
/// that was erased with `erase::<T>`. Calling `recover` with a different type than
/// was used for `erase` may panic or return incorrect data.
///
/// # Example
///
/// See [`AnyCast`].
/// In-process type erasure using `dyn Any`.
///
/// This is the default and most efficient strategy for same-process communication.
/// It uses Rust's [`Any`] trait for dynamic typing with zero serialization overhead.
///
/// # Example
///
/// ```
/// use linkem::dynch::{Cast, AnyCast};
///
/// let original: i32 = 42;
/// let erased = AnyCast::erase(original);
/// let recovered: i32 = AnyCast::recover(erased);
/// assert_eq!(recovered, 42);
/// ```
;
/// Alias for a [`Future`] trait object that can be [`Send`].
///
/// Note: it is lifetime-parameterized so it can borrow from the provided context.
pub type DynFuture<'a, T> = ;
/// A boxed function that, given a mutable reference to `Ctx`, produces a future.
///
/// The `for<'a>` makes this callable with *any* borrow lifetime of `&'a mut Ctx`,
/// and the returned future is allowed to live for that same `'a`.
pub type DynTask<Ctx, T> =
;
/// A dynamically typed request that can be created and sent when calling
/// [`DynRequestSender::submit`]. This is intended to ensure the correct type downcasting of the
/// result.
///
/// The `C` type parameter determines the type erasure strategy (defaults to [`AnyCast`]).
/// The response received after awaiting a [`DynRequestSender::submit`] request.
/// Internally, it holds a marker to the type needed for safe type downcasting.
///
/// The `C` type parameter determines the type erasure strategy (defaults to [`AnyCast`]).
/// The sender of [`DynRequest`].
///
/// The `C` type parameter determines the type erasure strategy (defaults to [`AnyCast`]).
/// A factory type for creating dynamic channels with specific type parameters.
///
/// # Type Parameters
///
/// - `Ctx`: The context type that will be available to tasks executed in the channel.
/// - `C`: The [`Cast`] strategy for type erasure (defaults to [`AnyCast`]).
///
/// # Examples
///
/// Using the default [`AnyCast`] strategy (most common):
///
/// ```
/// use linkem::dynch::DynCh;
///
/// struct MyContext {
/// data: Vec<u8>,
/// }
///
/// // Create a channel with MyContext, using default AnyCast
/// let (tx, rx) = DynCh::<MyContext>::channel(8);
/// ```