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
/// This macro performs a compile-time check if a struct has a specific field.
///
/// ## Syntax
///
/// The macro offers three syntaxes for checking if a struct has a field
///
/// 1. `assert_has_field!(Struct, field);` - checks if the struct has a field with the given name.
/// 2. `assert_has_field!(Struct, field: Type);` - checks if the struct has a field with the given name and type.
/// 3. `assert_has_field!(Struct, field :~ Type);` - checks if the struct has a field with the given name and type that can be coerced to the specified type `Type`.
///
/// ## Examples
///
/// ```rust
/// use assert_has_field::assert_has_field;
///
/// #[allow(dead_code)]
/// struct Point {
/// x: u64,
/// y: u64,
/// }
///
/// // This will compile because `Point` has a field `x`.
/// assert_has_field!(Point, x);
/// ```
///
/// If the field is not present, the macro will cause a compile-time error.
///
/// ```rust,compile_fail
/// use assert_has_field::assert_has_field;
///
/// #[allow(dead_code)]
/// struct Point {
/// x: u64,
/// y: u64,
/// }
///
/// // This will cause a compile-time error because `Point` does not have a field `a`.
/// assert_has_field!(Point, a);
/// ```
///
/// You can also specify the type of the field to ensure it matches a specific type.
///
/// ```rust
/// use assert_has_field::assert_has_field;
///
/// #[allow(dead_code)]
/// struct Point {
/// x: u64,
/// y: u64,
/// }
///
/// // This will compile because `Point` has a field `x` of type `u64`.
/// assert_has_field!(Point, x: u64);
/// ```
///
/// Note, however, that `:` syntax in this macro asserts the *exact* type of the field,
/// preventing any coercion to minimize the human error.
///
/// The following code will not compile:
///
/// ```rust,compile_fail
/// use assert_has_field::assert_has_field;
///
/// struct Wrapper<T>(T);
///
/// impl<T> core::ops::Deref for Wrapper<T> {
/// type Target = T;
///
/// fn deref(&self) -> &Self::Target {
/// &self.0
/// }
/// }
///
/// #[allow(dead_code)]
/// struct Point2 {
/// x: &'static Wrapper<u64>,
/// y: u64,
/// }
///
/// // This will cause a compile-time error because `Point2`'s field `x` is of type
/// // `&'static Wrapper<u64>`, not `&'static u64`.
/// assert_has_field!(Point2, x: &'static u64);
/// ```
///
/// Additionally, you can use the made-up `:~` syntax to assert that the field
/// can be coerced to the specified type.
///
/// ```rust
/// use assert_has_field::assert_has_field;
///
/// #[allow(dead_code)]
/// struct Wrapper<T>(T);
///
/// impl<T> core::ops::Deref for Wrapper<T> {
/// type Target = T;
///
/// fn deref(&self) -> &Self::Target {
/// &self.0
/// }
/// }
///
/// #[allow(dead_code)]
/// struct Point2 {
/// x: &'static Wrapper<u64>,
/// y: u64,
/// }
///
/// // This will compile because `Point2` has a field `x` that can be coerced to `&'static u64`.
/// assert_has_field!(Point2, x :~ &'static u64);
/// ```
///
/// ## On real use-cases
///
/// Let's say that you're writing a backend server and have a DTO, which is meant
/// to be used on the frontend. Assume that this DTO aggregates different kinds of
/// data that pertains to a candidate. You may be in a situation where `candidate_id`
/// is stored in one of the fields-structures. You can use [`assert_has_field`] to
/// document that expectation and future-proof the type in case the field-structure
/// that used to store `candidate_id` is removed entirely or modified in a way that
/// moves or removes the `candidate_id`.