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
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
//! # dymod
//!
//! This crate provides a macro, `dymod!`, which allows you to
//! specify a Rust module which will by dynamically loaded and
//! hotswapped in debug mode, but statically linked in release mode.
//!
//! The current version of this crate is very opinionated about how
//! you structure your dynamic code. Hopefully this can be relaxed a
//! little in future.
//!
//! ## Usage
//!
//! Your dynamically loaded code should be placed in its own
//! sub-crate under your main crate:
//!
//! ```text
//! mycrate/
//! Cargo.toml
//! src/
//! main.rs
//! subcrate/
//! Cargo.toml
//! src/
//! lib.rs
//! ```
//!
//! Your subcrate must also be compiled as a dylib, so in your
//! `subcrate/Cargo.toml` add:
//!
//! ```toml
//! [lib]
//! crate-type = ["dylib"]
//! ```
//!
//! Now you need to add the code that you want to hotswap. Any
//! functions should be `pub extern "C"` and `#[unsafe(no_mangle)]`.
//!
//! ```rust,no_run
//! // subcrate/src/lib.rs
//! #[unsafe(no_mangle)]
//! pub extern "C" fn count_sheep(sheep: u32) -> &'static str {
//! match sheep {
//! 0 => "None",
//! 1 => "One",
//! 2 => "Two",
//! 3 => "Many",
//! _ => "Lots"
//! }
//! }
//! ```
//!
//! Finally, use the `dymod!` macro to specify your module, along
//! with the functions that are dynamically available from it.
//!
//! ```rust,ignore
//! // src/main.rs
//! use dymod::dymod;
//!
//! dymod! {
//! #[path = "../subcrate/src/lib.rs"]
//! pub mod subcrate {
//! fn count_sheep(sheep: u32) -> &'static str;
//! }
//! }
//!
//! fn main() {
//! assert_eq!(subcrate::count_sheep(3), "Many");
//! loop {
//! // You can now edit the count_sheep function,
//! // recompile `subcrate`, and see the result change
//! // while this code is running.
//! println!("{}", subcrate::count_sheep(3));
//! }
//! }
//! ```
//!
//! ## Safety
//!
//! In release mode, the module you specify is linked statically
//! as if it was a regular module, and there should be no safety
//! concerns.
//!
//! However, in debug mode, when the code is being dynamically
//! linked, there are a lot of things that can go wrong. It's
//! possible to accidentally trigger panics, or undefined
//! behaviour.
//!
//! Here is a partial list of what can go wrong in debug mode:
//!
//! - If you are holding on to data owned by the dylib when the
//! dylib is hotswapped, you will get undefined behaviour.
//! - Unless both crates use the system allocator (which is luckily
//! the default since Rust 1.32.0) then dropping data that
//! was allocated by the other crate will cause a segfault.
//! - If you change the definition of a struct on either side of
//! the boundary, you could get undefined behaviour. (This
//! includes adding or removing enum variants.)
//! - If you specify the function signatures incorrectly in the
//! `dymod!` macro, you will get undefined behaviour.
//!
//! Because of these limitations, it is recommended that you use
//! a small number of dynamic functions, and pass types which are
//! unlikely to change much. For example, at the simplest:
//!
//! ```rust,ignore
//! use dymod::dymod;
//!
//! dymod! {
//! #[path = "../subcrate/src/lib.rs"]
//! pub mod subcrate {
//! fn update_application_state(state: &mut ApplicationState);
//! }
//! }
//! ```
//!
//! The above function would give you the flexibility to tweak any
//! application state at runtime, but the interface is simple enough
//! that it is easy to maintain.
//!
//! ## Manual reloading
//!
//! By default, the `auto-reload` feature is enabled, which will
//! reload the dynamic library whenever it changes (at the point
//! you try to call one of its functions).
//!
//! If you would prefer to handle reloading yourself, you can disable
//! the feature (`--no-default-features`) and reload it with the
//! `reload()` function of the dymod module.
//!
//! For this same reason, it is currently not possible to define
//! a function named `reload` within your dymod module.
compile_error!;
pub use ;
pub const AUTO_RELOAD: bool = cfg!;
) => ;
}
/// Takes a module definition and allows it to be hotswapped in debug
/// mode.
///
/// # Examples
///
/// ```rust,ignore
/// use dymod::dymod;
///
/// dymod! {
/// #[path = "../subcrate/src/lib.rs"]
/// pub mod subcrate {
/// fn count_sheep(sheep: u32) -> &'static str;
/// }
/// }
/// ```
///
/// This creates a module with a single function, `count_sheep`. In
/// debug mode, this function will call into the dynamically loaded
/// `subcrate` dylib. If that crate is recompiled, this function will
/// use the updated code.
///
/// In release mode, this module becomes just a regular Rust module
/// with the contents of `../subcrate/src/lib.rs`. No dynamic linking
/// is performed at all, and the functions are as safe as if they
/// were included normally in this crate.
///
/// # Panics
///
/// Beyond the normal risk of your code panicking, there are a few risks
/// associated with dynamic linking in debug mode. In release mode, static
/// linking occurs and those risks don't apply.
///
/// See the [crate-level documentation](index.html) for more information.
///
/// # Safety
///
/// As above, dynamic linking is inherently unsafe. In release mode,
/// static linking occurs and everything is safe. In debug mode,
/// a variety of undefined behavior is possible.
///
/// See the [crate-level documentation](index.html) for more information.
) =>
}