Better definition of async exceptions

[snoyberg]

syncIO previously relied upon the unexceptionalio package, which does
not use the standard definition from base of an asynchronous exception.
This brings errors in line with other libraries in the ecosystem for
recovering from all exceptions.

[Gabriella439]

I assume this is related to the discussion in singpolyma/unexceptionalio#9

I think this is a good change because it matches the stated contract of syncIO to ignore asynchronous exceptions. However, I'd like to preserve the old behavior under a function of a new name (i.e. unexceptionalIO or whatever), since I think it's useful to have a function which tries to squeeze as many exceptions out of IO as possible

[snoyberg]

The function you're describing would "squeeze" less exception types out of IO, not more. And any function that squeezes more types out of IO would allow recovering from an async exception, which would be broken behavior.

[Gabriella439]

Oh, weird. For some reason I thought that Unexceptional.fromIO just did a catch all on SomeException. Never mind, then. This is fine as is

[Gabriella439]

I'll wait three days before uploading to Hackage, just in case @singpolyma has any proposed changes

[snoyberg]

Awesome, thanks!

[Gabriella439]

You're welcome!

[singpolyma]

It's your package, of course. I'll just have to move the wrappers into my package or a new package for users who want what unexceptional offers.