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
//! # Traversable
//!
//! A trait for structures that can be traversed from left to right while preserving structure
//! and accumulating effects in an applicative functor.
//!
//! # Mathematical Definition
//!
//! For a type constructor `T`, a traversable instance consists of two operations:
//! - `traverse`: `(A -> F<B>) -> T<A> -> F<T<B>>`
//! - `sequence`: `T<F<A>> -> F<T<A>>`
//!
//! where `F` is an applicative functor.
//!
//! # Laws
//!
//! For a valid Traversable implementation, the following laws must hold:
//!
//! 1. **Identity**:
//! ```text
//! traverse(pure) == pure
//! ```
//! Traversing with `pure` is the same as lifting the structure into the applicative.
//!
//! 2. **Composition**:
//! ```text
//! traverse(Compose . fmap(g) . f) == Compose . fmap(traverse(g)) . traverse(f)
//! ```
//! Traversing with a composed function is the same as composing traversals.
//!
//! 3. **Naturality**:
//! ```text
//! t . traverse(f) == traverse(t . f)
//! ```
//! For any applicative transformation `t`, traversing then transforming equals
//! transforming then traversing.
//!
//! # Caveats
//!
//! ## `traverse_owned` and `FnOnce`
//!
//! The `traverse_owned` method uses `FnOnce` for its function parameter. This means:
//! - It works naturally for single-element containers (Option, Result)
//! - For multi-element containers (Vec), the function can only be called once,
//! which limits its usefulness
//!
//! If you need to traverse a multi-element container with ownership semantics,
//! consider using `traverse` with explicit cloning or a different approach.
use crateApplicative;
/// A trait for structures that can be traversed from left to right while preserving structure
/// and accumulating effects in an applicative functor.
///
/// # Type Parameters
///
/// * `Source` is the type of elements in the traversable structure
/// * `Output<T>` represents the structure containing elements of type `T`