You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This doesn't use fancy extensions that have come out since the 2009 paper Explicitly Typed Exceptions for Haskell, so the problem was there even in the original work. And this paper suggests exposing Caught to support explicitly typed user-created exception hierarchies. So in a way, we want to expose Caught as an implementation detail that can be extended. But we also want to discourage users from trying to use it directly.
So I'm thinking I'll create an “Internal” module with everything, and then re-export what's safe out in the normal module.
The text was updated successfully, but these errors were encountered:
This example shows how we can use
Caught
directly to bypass safety:This doesn't use fancy extensions that have come out since the 2009 paper Explicitly Typed Exceptions for Haskell, so the problem was there even in the original work. And this paper suggests exposing
Caught
to support explicitly typed user-created exception hierarchies. So in a way, we want to exposeCaught
as an implementation detail that can be extended. But we also want to discourage users from trying to use it directly.So I'm thinking I'll create an “Internal” module with everything, and then re-export what's safe out in the normal module.
The text was updated successfully, but these errors were encountered: