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
//! Raw `ClassLayout` table representation.
//!
//! This module provides the [`crate::metadata::tables::classlayout::raw::ClassLayoutRaw`] struct
//! for low-level access to `ClassLayout` metadata table data with unresolved table indexes.
//! This represents the binary format of `ClassLayout` records as they appear in the metadata
//! tables stream, requiring resolution to create usable data structures.
//!
//! # Architecture
//!
//! The raw representation maintains the exact binary layout from the metadata tables stream,
//! with unresolved table indexes that reference other metadata tables. This design allows
//! efficient parsing and deferred resolution until references are needed.
//!
//! # Key Components
//!
//! - [`crate::metadata::tables::classlayout::raw::ClassLayoutRaw`] - Raw table row structure with unresolved indexes
//! - [`crate::metadata::tables::classlayout::raw::ClassLayoutRaw::to_owned`] - Resolution to owned representation
//! - [`crate::metadata::tables::classlayout::raw::ClassLayoutRaw::apply`] - Direct application of layout data
//!
//! # `ClassLayout` Table Format
//!
//! The `ClassLayout` table (0x0F) contains zero or more rows with these fields:
//! - **`PackingSize`** (2 bytes): Field alignment boundary (power of 2)
//! - **`ClassSize`** (4 bytes): Total size of the type in bytes
//! - **Parent** (2/4 bytes): Table index into `TypeDef` table
//!
//! # Usage Examples
//!
//! ```rust,ignore
//! # use dotscope::metadata::tables::classlayout::ClassLayoutRaw;
//! # use dotscope::metadata::typesystem::TypeRegistry;
//! # fn example(raw: ClassLayoutRaw, types: &TypeRegistry) -> dotscope::Result<()> {
//! // Convert to owned representation
//! let owned = raw.to_owned(types)?;
//!
//! // Or apply layout data directly
//! raw.apply(types)?;
//! # Ok(())
//! # }
//! ```
//!
//! # Error Handling
//!
//! Raw table operations can fail if:
//! - Referenced `TypeDef` entries are missing from the provided registry
//! - Type definition tokens are invalid or malformed
//! - Layout validation fails (invalid packing or class sizes)
//! - Table data is corrupted or incomplete
//!
//! # Thread Safety
//!
//! Raw table structures are [`Send`] and [`Sync`]. The `apply` method uses atomic operations
//! when updating type definition data, ensuring thread-safe modifications.
//!
//! # Integration
//!
//! This module integrates with:
//! - [`crate::metadata::tables::classlayout::owned`] - Owned representation with resolved references
//! - [`crate::metadata::typesystem`] - Type system components and registry
//! - [`crate::metadata::validation`] - Layout validation logic
//! - [`crate::metadata::tables`] - Core metadata table infrastructure
//! - [`crate::metadata::token`] - Token-based metadata references
//!
//! # References
//!
//! - [ECMA-335 II.22.8](https://ecma-international.org/wp-content/uploads/ECMA-335_6th_edition_june_2012.pdf) - `ClassLayout` table specification
use Arc;
use crate::;
/// Raw `ClassLayout` table row with unresolved table indexes
///
/// Represents the binary format of a `ClassLayout` metadata table entry (table ID 0x0F) as stored
/// in the metadata tables stream. The Parent field contains a table index that must be
/// resolved using the [`crate::metadata::typesystem::TypeRegistry`] to access the referenced type data.
///
/// The `ClassLayout` table specifies explicit memory layout information for types that require
/// specific field positioning and packing, commonly used for interoperability scenarios.
///
/// # Memory Layout Control
///
/// The `ClassLayout` entry provides precise control over type memory representation:
/// - **`PackingSize`**: Byte boundary alignment for fields (must be power of 2)
/// - **`ClassSize`**: Explicit type size override (0 for automatic sizing)
/// - **Parent**: Link to the type definition requiring these layout constraints
///
/// # Conversion and Usage
///
/// Raw entries should be converted to [`crate::metadata::tables::classlayout::owned::ClassLayout`]
/// via [`crate::metadata::tables::classlayout::raw::ClassLayoutRaw::to_owned`] for practical use,
/// or have their layout data applied directly via [`crate::metadata::tables::classlayout::raw::ClassLayoutRaw::apply`].
///
/// # Thread Safety
///
/// This type is [`Send`] and [`Sync`]. Methods that update type definitions use atomic
/// operations to ensure thread-safe modifications without additional synchronization.
///
/// # References
///
/// - [ECMA-335 II.22.8](https://ecma-international.org/wp-content/uploads/ECMA-335_6th_edition_june_2012.pdf) - `ClassLayout` table specification