Use explicit `forall` on most functions to allow exception type to be pinned more easily

[3noch]

With -XTypeApplications you can do this with base's try: try @HttpException $ do... which is pretty handy. But with safe-exceptions you must do try @IO @HttpException. If the type parameters were explicitly ordered the other way around, the @IO could be "curried", i.e. left for type inference, more easily.

[bitemyapp]

Just wondering, does try @_ @HttpException work for you?

[3noch]

@bitemyapp I should have mentioned that. I thought it required -XPartialTypeSignatures but I see that it does not. That certainly helps. Ideally, though, I think one would be able to simply change the import Control.Exception (...) import to import Control.Exception.Safe (...) and not have to change anything else.

[3noch]

@bitemyapp Thanks for bringing that up.

[snoyberg]

I'm pretty terrified at how easily we can introduce breaking changes into the public API of a package thanks to TypeApplications. I'm not too terribly excited about supporting this workflow as a result, but I'll accept a PR with the change.