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
//! Zond is crate with standard rust collections but with collecting statistics.
//!
//! Ok, maybe it contains only analogue of [`Vec`] - [`zvec::ZVec`]. And ok, `ZVec` contains only some part of `Vec` methods.
//! But I made this just for fun. I don't know anyone who would really need this.
//!
//! # Example
//!
//! Let's start from constructing collection.
//!
//! Constructors similar to their std analogues' constructors but have additional argument - struct [`Zond`] with two fields:
//! 1. `zond_handler` of type [`ZondHandler`]. \
//! Trait object with single method that consumes two arguments: `id` as [`usize`] and `operations` as [`Operations`].
//! All operations handling is hapeppening here: you can save them to file or database, send to your server or just print to console.
//! 2. `policy` of type [`Policy`]. \
//! Desribes the rules about when collected operations will handled by `zond_handler`.
//! ```
//! # use std::{fmt::Debug, num::NonZeroUsize};
//! # use zond::{OperationType, ZondHandler, Operations, Zond, Policy, zvec::{ZVec, ZVecOperation}};
//! // So at first let's implement some ZondHandler. It will just print operations to stdout:
//! struct HandlerImpl;
//!
//! impl<T: OperationType + Debug> ZondHandler<T> for HandlerImpl {
//! fn handle(&self, id: usize, operations: Operations<T>) {
//! println!("{id} collected");
//! operations
//! .iter()
//! .for_each(|v| println!("{:?}: {:?}", v.get_instant(), v.get_type()));
//! println!();
//! }
//! }
//!
//! # fn main() {
//! // Next let's construct Zond with HandlerImpl handler and such a policy that operations will be handled after each three method calls.
//! // It will handle operations for ZVec:
//! let zond: Zond<ZVecOperation<usize>> = Zond::new(
//! HandlerImpl,
//! Policy::on_count_operations(NonZeroUsize::new(3).unwrap()),
//! );
//!
//! // Next let's construct ZVec with zond variable:
//! let mut zvec: ZVec<usize> = ZVec::new(zond);
//!
//! // Finally let's execute some operations:
//! zvec.push(1);
//! zvec.push(2);
//! zvec.push(5);
//! zvec.push(5);
//! zvec.extend_from_within(1..);
//! zvec.dedup();
//! drop(zvec);
//! # }
//! ```
//!
//! The console output will look like this:
//! ```text
//! 0 collected
//! Instant { /* */ }: New
//! Instant { /* */ }: Push { value: 1 }
//! Instant { /* */ }: Push { value: 2 }
//!
//! 0 collected
//! Instant { /* */ }: Push { value: 5 }
//! Instant { /* */ }: Push { value: 5 }
//! Instant { /* */ }: ExtendFromWithin { src_start_bound: Included(1), src_end_bound: Unbounded }
//!
//! 0 collected
//! Instant { /* */ }: Dedup
//! ```
//!
//! As you can see, operations always being handled when dropping.
use ;
pub use Policy;
use PolicyInner;
static ID_GENERATOR: AtomicUsize = new;
/// Helper trait for constrainting generic types in other structs and traits. \
/// `OperationType` unites multiple collection-specific enums. But in fact only [`ZVec`](zvec::ZVec)'s [`ZVecOperation`](zvec::ZVecOperation).
/// Describes one single operation with collection: time when it happened and operation type.
/// Just type alias for more convenient types declaring in other places.
pub type Operations<T> = ;
/// Provides function that handle all operations with collection.
///
/// # Example
/// ```no_run
/// # use std::fmt::Debug;
/// # use zond::{ZondHandler, Operations, OperationType};
/// struct HandlerImpl;
///
/// impl<T: OperationType + Debug> ZondHandler<T> for HandlerImpl {
/// fn handle(&self, id: usize, operations: Operations<T>) {
/// for operation in operations {
/// println!("{:?}", operation.get_type());
/// }
/// }
/// }
/// ```
/// Struct that controls how and when to handle operations.
// Crucial part of the crate. This struct contains all other structs, trait object and enums that take part in storing and handling operations. \
// Must be aggregated in structs that implement some collection's functionality.
pub