Skip to content

Safe Haskell compatability #493

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Safe Haskell compatability #493

wants to merge 2 commits into from

Conversation

deian
Copy link

@deian deian commented Apr 21, 2012

This patch makes pretty much every module of pandoc Trustworthy. I hope to convince the authors of the packages pandoc depends on to make their packages Trustworthy, at which point we can turn many of the Trustworthy modules to Safe. If there is some particular module that is not safe, please let me know.

Deian Stefan and others added 2 commits April 10, 2012 03:54
From a brief look at the API, it all seems safe, so I'm currently
labeling all the modules Trustworthy.

TODO: some of the modules may (but are unlikely to) be Safe. In a
later verison, when parsec etc. are labeled Trustworthy, most of the
modules exported by this package can conceivably simply be Safe.
@jgm
Copy link
Owner

jgm commented Apr 29, 2012

I don't know anything about these new GHC extensions. Could you explain what is meant by the Trustworthy classification, and what impact it has?

@deian deian closed this Apr 15, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants