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
//! Interfaces of [Ur](crate::ur::Ur) and related types.
//!
//! # Thread safety
//! In this crate, there are some similar types providing undo-redo functionality, e.g.
//! [Ur](crate::ur::Ur) and [Aur](crate::aur::Aur).
//! They have almost the same methods.
//! Unfortunately, however, the trait bounds in some methods are a bit different.
//!
//! The reason why is thread safety.
//! The [Ur](crate::ur::Ur) does not require closures implementing [Send] and [Sync] in some methods (e.g. [edit](crate::ur::Ur::edit)).
//! So [Ur](crate::ur::Ur)'s internal history data can not be thread-safe because the closures are stored as records in it.
//!
//! Unlike [Ur](crate::ur::Ur), [Aur](crate::aur::Aur) requires closures implementing [Send] and [Sync].
//! Therefore, [Aur](crate::aur::Aur) can implement [Send] and [Sync] because all of stored closures are guaranteed
//! to be thread-safe objects.
//!
//! To clarify the differences,
//! their interfaces are defined as traits in this module.
//!
//! All types in this crate implements some of the interface traits as appropriate.
//! Mappings between types and the traits are listed below.
//!
//! # Interface for undo-redo types
//! | Type | Trait |
//! | :------------------------ | :--------------------- |
//! | [Ur](crate::ur::Ur) | [IUndoRedo] + [IEdit] |
//! | [Cur](crate::cur::Cur) | [IUndoRedo] + [IEdit] |
//! | [Aur](crate::aur::Aur) | [IUndoRedo] + [IEditA] |
//! | [Acur](crate::acur::Acur) | [IUndoRedo] + [IEditA] |
//!
//! # Interface for builder types
//! | Type | Trait |
//! | :-------------------------------------- | :----------------------- |
//! | [UrBuilder](crate::ur::UrBuilder) | [IBuilder] + [ITrigger] |
//! | [CurBuilder](crate::cur::CurBuilder) | [IBuilder] + [ITrigger] |
//! | [AurBuilder](crate::aur::AurBuilder) | [IBuilder] + [ITriggerA] |
//! | [AcurBuilder](crate::acur::AcurBuilder) | [IBuilder] + [ITriggerA] |
//!
//! # `edit` with side effects
//! [Ur](crate::ur::Ur) family have methods to change their state; [edit](IEdit::edit), [edit_if](IEdit::edit_if), and [try_edit](IUndoRedo::try_edit).
//! Users should choose which method to use depending on a closure has side effects.
//!
//! ## `edit` and `edit_if`
//! [edit](IEdit::edit) and [edit_if](IEdit::edit_if) MUST take closures that produces a same result for a same input.
//! The reason why is that the closures are stored in the history and used reproducing old states
//! for undoing.
//!
//! ## `try_edit`
//! [try_edit](IUndoRedo::try_edit) accepts closures that can never reproduce same output again.
//!
//! Generally, closures including following functions should use [try_edit](IUndoRedo::try_edit):
//!
//! - I/O
//! - IPC
//! - random
//!
//! etc.
use crateMetrics;
/// A common interface for [Ur](crate::ur::Ur) and othres.
///
/// Following traits provides additional interfaces.
/// - [IEdit]
/// - [IEditA]
///
/// See [module-level documentation](crate::interface) for more details.