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
//! `FieldLayout` table loader implementation.
//!
//! This module provides the [`crate::metadata::tables::fieldlayout::loader::FieldLayoutLoader`] responsible for loading and processing
//! `FieldLayout` metadata table entries. The `FieldLayout` table specifies explicit field
//! positioning within types, defining the byte offset of fields in classes and value types.
//!
//! # Purpose
//! The `FieldLayout` table is used when explicit field layout control is needed, such as:
//! - Interop scenarios requiring specific memory layouts
//! - Performance-critical structures with cache-line awareness
//! - Platform-specific data structure alignment
//! - COM interop and P/Invoke marshalling
//!
//! # Table Dependencies
//! - **Field table**: Required for field reference resolution
//!
//! # ECMA-335 Reference
//! See ECMA-335, Partition II, §22.16 for the `FieldLayout` table specification.
use crate::;
/// Loader implementation for the `FieldLayout` metadata table.
///
/// This loader processes `FieldLayout` table entries which specify the explicit
/// byte offset of fields within their containing types. Field layout information
/// is essential for interop scenarios and performance-critical data structures
/// where precise memory layout control is required.
///
/// # Error Conditions
/// Loading may fail if:
/// - Field references cannot be resolved
/// - Invalid field offset values are encountered
/// - Memory allocation fails during processing
/// - Concurrent access conflicts occur
///
/// # ECMA-335 Reference
/// See ECMA-335, Partition II, §22.16 for complete `FieldLayout` table specification.
pub ;