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
//! [](https://github.com/boltlabs-inc/vesta/actions/workflows/rust.yml)
//! 
//! [](https://crates.io/crates/vesta)
//! [](https://docs.rs/vesta)
//!
//! > A **vesta**, otherwise known as a *match case*, is a small container for matches, named
//! > after the Roman goddess of the hearth.
//! >
//! > **Vesta** is a crate for extensibly *matching cases* in Rust.
//!
//! By implementing [`Match`](Match@trait) and [`Case`] for some type (or better yet, correctly
//! deriving them using the [`Match`](Match@macro) derive macro), you can pattern-match on that type
//! using the [`case!`] macro almost like using the `match` keyword built into Rust.
//!
//! However, Vesta's [`case!`] macro is more general than `match`, because [`Match`] and [`Case`]
//! are traits! This means you can enable pattern-matching for types which are not literally
//! implemented as `enum`s, and you can write code which is generic over any type that is
//! pattern-matchable.
// Documentation configuration
pub use ;
/// This module is exported so that the `derive_match!` macro can make reference to `vesta` itself
/// from within the crate.
/// A type which is [`Match`] can be pattern-matched using the [`case!`] macro and the methods of
/// [`CaseExt`]/[`Case`].
///
/// In order for a type to be matched, it must implement [`Match`], as well as [`Case`] for each
/// distinct case it can be matched against.
pub unsafe
/// An extension trait providing methods analogous to those in [`Case`], but which take `self` and
/// type parameters.<br>💡 Prefer using these to directly calling the methods in [`Case`].
/// Statically assert that the type of the given value is exhaustive for `N`.
///
/// This function can only be called if `Self: Match<Range = Exhaustive<N>>`. It does nothing
/// when called.
///
/// # Examples
///
/// ```
/// vesta::assert_exhaustive::<_, 2>(&Some(true));
/// ```
/// Mark an unreachable location in generated code.
///
/// # Panics
///
/// In debug mode, panics immediately when this function is called.
///
/// # Safety
///
/// In release mode, undefined behavior may occur if this function is ever called.
pub unsafe
/// A marker type indicating that the [`tag`](Match::tag) for some type will always be *strictly
/// less than* `N`.
///
/// Use this to mark the [`Range`](Match::Range) of exhaustive enumerations.
/// A marker type indicating that the [`tag`](Match::tag) for some type is not fixed to some known
/// upper bound.
///
/// Use this to mark the [`Range`](Match::Range) of non-exhaustive enumerations.
/// An implementation of [`Case`] defines a particular case of a pattern match for a type.<br> ℹ️
/// Prefer using the methods of [`CaseExt`] to directly calling these methods.