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
//! Message-id to message lookup.
//!
//! The reference engine keeps a per-connection dictionary
//! (`outstanding_msgs_dict`) keyed on `msgid_t` so that a response
//! arriving on the wire can be paired with its outstanding request in
//! constant time. Earlier stages introduced
//! [`crate::util::dict::MsgIndex`] (an `ahash`-backed
//! [`std::collections::HashMap`]) keyed on [`MsgId`]; this module
//! provides the message-flavored alias plus a thin newtype that adds
//! the verbs the message layer actually uses.
//!
//! [`MsgId`]: crate::core::types::MsgId
use crateMsgId;
use crateDictMap;
use Msg;
/// Owning index of [`Msg`] values keyed on [`MsgId`].
///
/// The C engine stores `struct msg *` pointers; the Rust port owns
/// the value directly so dropping the index releases every contained
/// message. Lookups return references; transferring ownership out of
/// the index requires [`MsgIndex::remove`].
///
/// # Thread safety
///
/// `MsgIndex` mirrors the reference engine's `outstanding_msgs_dict`,
/// which is per-connection and accessed only from the connection's
/// owning event-loop thread. The Rust port preserves that
/// single-threaded contract: `MsgIndex` is `Send` (it can be moved
/// to another task or thread, e.g. when a connection migrates) but
/// is intentionally not exposed through any synchronisation
/// primitive. The wrapped [`std::collections::HashMap`] inside
/// [`DictMap`](crate::util::dict::DictMap) is not `Sync`, so two
/// tasks cannot share a `&MsgIndex` and call its mutating methods
/// concurrently. Stages 9 and beyond keep the index private to the
/// per-connection FSM; if a future caller ever needs cross-thread
/// shared access, that caller is responsible for wrapping it in a
/// `Mutex` (or equivalent), not the type itself.