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
pub use NewPoolItemError;
use crate::;
use Debug;
use ;
/// The core trait for types managed by a [`ThreadPool`](crate::ThreadPool).
///
/// A `PoolItem` is a stateful object that:
/// - Lives on a single thread for its entire lifetime
/// - Has a unique ID within the pool
/// - Communicates via typed request/response messages
/// - Can own non-`Send`/`Sync` types like `Rc<RefCell<T>>`
///
/// # Using the `#[pool_item]` Macro (Recommended)
///
/// The easiest way to implement `PoolItem` is with the `#[pool_item]` attribute macro,
/// which generates all the boilerplate automatically:
///
/// ```rust
/// use messaging_thread_pool::{IdTargeted, pool_item};
///
/// #[derive(Debug)]
/// pub struct Counter {
/// id: u64,
/// value: i32,
/// }
///
/// impl IdTargeted for Counter {
/// fn id(&self) -> u64 { self.id }
/// }
///
/// #[pool_item]
/// impl Counter {
/// pub fn new(id: u64) -> Self {
/// Self { id, value: 0 }
/// }
///
/// #[messaging(IncrementRequest, IncrementResponse)]
/// pub fn increment(&mut self, amount: i32) -> i32 {
/// self.value += amount;
/// self.value
/// }
/// }
/// ```
///
/// # Associated Types
///
/// - **`Init`**: The request type used to create new instances (e.g., `CounterInit(u64)`)
/// - **`Api`**: An enum of all message types the pool item can handle
/// - **`ThreadStartInfo`**: Optional per-thread state (e.g., for tracing configuration)
///
/// # Lifecycle
///
/// 1. **Creation**: When an `Init` request is received, `new_pool_item` is called
/// 2. **Processing**: Messages are delivered to `process_message` sequentially
/// 3. **Shutdown**: `shutdown_pool` is called when the pool is dropped
///
/// # Thread Affinity
///
/// Pool items are assigned to threads using `id_thread_router(id, thread_count)`.
/// The default implementation is `id % thread_count`. All messages for the same ID
/// go to the same thread, ensuring sequential processing without locks.
///
/// # Manual Implementation
///
/// For advanced use cases or when the macro isn't suitable, you can implement
/// `PoolItem` manually. See the [`samples`](crate::samples) module for examples.