Skip to content
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

Deprecation reason #36

Open
andrewthad opened this issue Oct 2, 2015 · 1 comment
Open

Deprecation reason #36

andrewthad opened this issue Oct 2, 2015 · 1 comment

Comments

@andrewthad
Copy link

This package is marked as deprecated on hackage. I could imagine dozens of reasons why you would choose to do this, and it doesn't bother me that you did. However, knowing why you did would be helpful for me (and I think for others as well) if we're trying to decide to use this package for something. If it was "I don't want to maintain this anymore, and it won't work with newer versions of lens", then I might still try to use it out for a small project. If it was "The implementation is incorrect and it gives bad results on occasion", then I would never use it. Even adding a one-line explanation of the deprecation reason in the readme would but sufficient for this and helpful for me.

@ekmett
Copy link
Owner

ekmett commented Oct 2, 2015

The main issue is that #15 has never been fixed. If that was fixed I'd undeprecate in a heartbeat, but I haven't had any time to go back and revisit it, so I figured it was safer to just mark the package as deprecated for now.

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

No branches or pull requests

2 participants