@@ -135,13 +135,14 @@ there is a problem with the teardown itself, an error would be raised right at
135135the moment of cancellation which we must either handle, or allow to propagate
136136before attempting another turn of the loop.
137137
138- The bad news is of course, that no matter how much we wish abort controllers
139- worked this way, the fact of the matter is that they do not. Instead of being a
140- general tool for coordinating shutdown, they are nothing more than a channel
141- that communicates an intent to do so. And when we use them, we are forced to
142- muddle through the actual work of an orderly cancellation and hope that all the
143- functions we pass our signal too can do the same. It should go without saying
144- however that robust APIs are not built on hope.
138+ The bad news is of course, that no matter how much we wish abort
139+ controllers worked this way, They don't. Instead of being a general
140+ tool for coordinating shutdown, they are nothing more than a channel
141+ that communicates an intent to do so. And when we use them, we are
142+ forced to muddle through the actual work of an orderly cancellation
143+ and hope that all the functions we pass our signal too can do the
144+ same. It should go without saying however that robust APIs are not
145+ built on hope.
145146
146147There is some good news though: You don’t have to deal with the headaches of an
147148abort controller _at all_ when you have a
0 commit comments