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
//! Provides TokioTp executor specific functionality.
//
use
;
/// An executor that uses [tokio::runtime::Runtime].
///
/// ## Example
///
/// The following example shows how to pass an executor to a library function.
///
/// ```rust
/// use
/// {
/// futures :: { task::{ Spawn, SpawnExt } } ,
/// async_executors :: { TokioTpBuilder } ,
/// tokio::runtime :: { Builder } ,
/// std::convert :: { TryFrom } ,
/// futures::channel :: { oneshot, oneshot::Sender } ,
/// };
///
///
/// fn lib_function( exec: impl Spawn, tx: Sender<&'static str> )
/// {
/// exec.spawn( async
/// {
/// tx.send( "I can spawn from a library" ).expect( "send string" );
///
/// }).expect( "spawn task" );
/// }
///
///
/// fn main()
/// {
/// // You must use the builder. This guarantees that TokioTp is always backed up by a threadpool.
/// // You can set other configurations by calling `tokio_builder()` on TokioTpBuilder, so you get
/// // access to the `tokio::runtime::Builder`.
/// //
/// let exec = TokioTpBuilder::new().build().expect( "create tokio threadpool" );
///
/// let program = async
/// {
/// let (tx, rx) = oneshot::channel();
///
/// lib_function( &exec, tx );
/// assert_eq!( "I can spawn from a library", rx.await.expect( "receive on channel" ) );
/// };
///
/// exec.block_on( program );
/// }
/// ```
///
///
/// ## Unwind Safety.
///
/// You must only spawn futures to this API that are unwind safe. Tokio will wrap it in
/// [std::panic::AssertUnwindSafe] and wrap the poll invocation with [std::panic::catch_unwind].
///
/// They reason that this is fine because they require `Send + 'static` on the future. As far
/// as I can tell this is wrong. Unwind safety can be circumvented in several ways even with
/// `Send + 'static` (eg. `parking_lot::Mutex` is `Send + 'static` but `!UnwindSafe`).
///
/// You should make sure that if your future panics, no code that lives on after the spawned task has
/// unwound, nor any destructors called during the unwind can observe data in an inconsistent state.
///
/// If a future is run with `block_on` as opposed to `spawn`, the panic will not be caught and the
/// thread calling `block_on` will be unwound.
///
/// Note that unwind safety is related to logic errors, not related to the memory safety issues that cannot happen
/// in safe rust (memory safety, undefined behavior, unsoundness, data races, ...). See the relevant
/// [catch_unwind RFC](https://github.com/rust-lang/rfcs/blob/master/text/1236-stabilize-catch-panic.md)
/// and it's discussion threads for more info as well as the documentation of [std::panic::UnwindSafe].
//
//
//