Since exception can arise at any point, it is not possible to guarantee atomicity of operation, hence mutable data structure may remain in incorrect state in case of interruption.
Even if async exceptions didn't exist, we couldn't guarantee atomicity in
general without specifically atomic functions (like atomicModifyIORef or
STM), since another thread may access the data concurrently and create a
data race.
If you're only talking about single-threaded cases—of which ST is
_basically_ a subset[1]—I don't think you're really worried about
_atomicity_, but about exception safety. Exception safety goes beyond async
exceptions, since almost all IO actions can throw some form of synchronous
exception. For those cases, you can use one of the many exception-cleanup
functions, like finally, onException, bracket, or bracketOnError.
It's true that those functions don't work inside ST, but I'd argue you
don't need them to. The expected behavior of code that receives an async
exception is to (1) clean up after itself and (2) rethrow the exception.
But as ST blocks are supposed to be free of externally-visible side
effects, worrying about putting its variables back into some safe state is
unnecessary[2].
To summarize:
* If you need true atomicity, you're in IO and dealing with multiple
threads. I'd recommend sticking with STM unless you have a strong reason to
do otherwise.
* If you are single threaded and in IO, you can get away with non-STM stuff
more easily, and need to make sure you're using exception-aware functions.
* If you're inside ST, make sure any resources you acquire are cleaned up
correctly, but otherwise you needn't worry about exceptions.
Also, you may be interested in reading the documentation for
safe-exceptions[3], which talks more about async exception safety.
[1] I say basically since you'd have to pull out unsafe functions to fork a
thread that has access to an STVar or similar, though it could be done.
[2] If you're doing something like binding to a C library inside ST, you
may have some memory cleanup to perform, but the STVars and other data
structures should never be visible again.
[3] https://haskell-lang.org/library/safe-exceptions
On Thu, Sep 28, 2017 at 2:00 PM, Станислав Черничкин wrote: It's quite hard to implement mutable data structures in presence of
asynchronous exceptions. Since exception can arise at any point, it is not
possible to guarantee atomicity of operation, hence mutable data structure
may remain in incorrect state in case of interruption. One can certainly
use maskAsyncExceptions# and friends to protect critical regions, but
masking function are living in IO, mutable data structures on other hand
trend to be state-polymorphic (to allow it usage in ST). This lead to conflicting requirements:
- One should not care about asynchronous exceptions inside ST (it is not
possible to catch exception in ST, hence not possible to use something in
invalid state). More over, it is not even possible to do write
“exception-safe” code, because masking functions not available.
- One should provide accurate masking then using same data structures in
IO. So I want do discuss several questions topics on this case. 1. Impact. Are async exceptions really common? Would not be easier to say:
“ok, things can go bad if you combine async exceptions with mutable data
structures, just don't do it”. 2. Documentation. Should library authors explicitly mention async
exceptions safety? For example https://hackage.haskell.org/
package/hashtables – is it async exceptions safe when used in IO? Or even
worse https://hackage.haskell.org/package/ghc-prim-0.5.1.0/docs/
GHC-Prim.html#v:resizeMutableByteArray-35- - what will happened in case
of async exception? This functions is sate-polimorphic, will it implicitly
mask exceptions if used from IO? 3. Best practices. How should we deal with problem? Is creating separate
versions of code for ST and IO is the only way? Probably it is possible to
add “mask” to something like https://hackage.haskell.org/
package/primitive-0.6.2.0/docs/Control-Monad-Primitive.html#t:PrimMonad
emit mask in IO instance and NOOP in ST version? Or maybe somebody know
better patterns for async exeption safe code? --
Sincerely, Stanislav Chernichkin. _______________________________________________
Haskell-Cafe mailing list
To (un)subscribe, modify options or view archives go to:
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
Only members subscribed via the mailman list are allowed to post.