Removing deprecated modules and packages #92
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As things are, this repository contains three different variants of the same code providing the same functionality (across two packages). Two have been deprecated for at least three years. The presence of these two deprecated versions makes the package less appealing and harder to interact with (both on GitHub, and on Hackage).
There is an argument that the best location for this library is
Data.Witherable
, notWitherable
(by analogy withData.{Foldable,Traversable,Functor}
). However, I think the best way to do this is in two parts: get down to one single package with one single module now, and then (maybe later) talk about what that one module should be called.